This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-09-13
Channels
- # announcements (1)
- # babashka (12)
- # beginners (10)
- # biff (9)
- # calva (2)
- # cherry (21)
- # cider (14)
- # clj-commons (76)
- # clj-kondo (8)
- # clj-on-windows (34)
- # cljs-dev (5)
- # clojure (48)
- # clojure-austin (7)
- # clojure-europe (97)
- # clojure-nl (1)
- # clojure-norway (14)
- # clojure-uk (22)
- # clojurescript (137)
- # conjure (33)
- # cursive (4)
- # datalevin (1)
- # deps-new (4)
- # devcards (2)
- # duct (3)
- # events (1)
- # fulcro (12)
- # graphql (9)
- # hyperfiddle (16)
- # jobs (8)
- # kaocha (1)
- # leiningen (6)
- # lsp (39)
- # malli (38)
- # membrane (20)
- # nbb (68)
- # observability (7)
- # off-topic (49)
- # pathom (11)
- # polylith (8)
- # portal (22)
- # re-frame (6)
- # releases (1)
- # remote-jobs (2)
- # shadow-cljs (24)
- # spacemacs (2)
- # squint (6)
- # xtdb (7)
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
That's OK - "throw an autocmd on it" has been a viable solution to most of my Vim problems for years! 😄
Did you update nvim or other plugins recently? I currently have no idea what's causing this or how to reproduce it 😞
I regularly update nvim and all of my plugins every few days. And I have a ton of plugins. So the possibilities are many
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?
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:
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.
I only ever use stable released Neovim versions, so I need to work out how to try unstable
Have you thought about running the various Neovim versions in CI and taking screenshots? (if such a thing is possible in CI)
Another thought: a local Dockerized setup could allow you to easily try other Neovim versions without having them installed on your machine
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.
Conjure isn't even in the business of setting ft=whatever, it's just using file extensions
Neovim should be setting the ft correctly based on the extension, but in this case, it's not
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
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
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
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: