Fork me on GitHub
#conjure
<
2022-09-13
>
dave18:09:40

https://clojurians.slack.com/archives/CK143P6D7/p1662049968122479 I'm still having issues with Conjure not automatically setting the log buffer's ft to clojure, for some reason. I came up with a workaround just now, though, which works well:

autocmd BufEnter conjure-log-*.cljc set ft=clojure

Olical18:09:07

Second person to have that issue and I have absolutely no idea why :(

dave18:09:17

That's OK - "throw an autocmd on it" has been a viable solution to most of my Vim problems for years! 😄

dave18:09:32

(and probably the source of some of them, too)

Olical18:09:43

Did you update nvim or other plugins recently? I currently have no idea what's causing this or how to reproduce it 😞

dave18:09:13

I regularly update nvim and all of my plugins every few days. And I have a ton of plugins. So the possibilities are many

Olical18:09:20

Any thoughts on what might have changed are appreciated. I haven't done anything to change this (intentionally) inside conjure. Are you on the develop branch?

Olical18:09:28

Are you using stable Neovim or a nightly?

dave18:09:55

Unstable Neovim, master branch of Conjure

dave18:09:39

Off-hand, I can't think of any plugin I use that would potentially interfere with Conjure's ability to set the ft on its log buffer :thinking_face:

Olical18:09:50

Okay, so you and the other person are using unstable Neovim. My hunch is that they introduced a breaking change I haven't noticed and haven't worked around yet.

Olical18:09:56

I hope. If it's not that I'm at a loss.

Olical18:09:10

I only ever use stable released Neovim versions, so I need to work out how to try unstable

dave18:09:54

Have you thought about running the various Neovim versions in CI and taking screenshots? (if such a thing is possible in CI)

dave18:09:53

Another thought: a local Dockerized setup could allow you to easily try other Neovim versions without having them installed on your machine

Olical18:09:04

I've thought about adding integration tests before but not really across versions, I only target and support stable really right now. But could be worth looking into one day.

Olical18:09:15

I think there's a cli that lets you swap nvim versions easily

Olical18:09:18

Some community tool

Olical18:09:31

I'll look around, mostly concerned at how I've missed a breaking change this big

Olical18:09:38

I don't even set the file type or anything

Olical18:09:42

I just set the file extension

Olical18:09:00

That's all. So how has THAT stopped working... maybe a bug with floating windows...

dave18:09:20

Ohh, yeah. In light of that, this bug is super weird

dave18:09:41

Conjure isn't even in the business of setting ft=whatever, it's just using file extensions

dave18:09:53

Neovim should be setting the ft correctly based on the extension, but in this case, it's not

dave19:09:08

If I do :e /tmp/foo.cljc, that works fine, and it sets ft=clojure

dave19:09:26

Could be related to floating windows?

dave19:09:55

I was seeing the ft not getting set in the floating window, and then when I pressed <localleader>lt to bring up the log "full screen," the ft still wasn't set. I wonder if the fact that it initially appears as a floating window is important

Olical19:09:50

My hunch too, will have to look soon, will only get more people running into this, especially if they don't fix it and it is a Neovim bug. I wonder if nvim has any open issues

dave19:09:38

If I do :e while viewing the Conjure log buffer, the buffer empties out, and the ft is still not set. For whatever that's worth

Olical09:09:05

Kinda smells like this to me https://github.com/neovim/neovim/pull/19216 There's an option you can set to use the legacy filtype.vim file. No idea why the .lua version would work differently, maybe it is a bug and we're the first to notice it but I find that unlikely. I can't see any issues on the nvim github that sound like this :thinking_face: