Fork me on GitHub
#vim
<
2022-07-18
>
dave20:07:54

Anyone else here using the Neovim unstable branch?

dave20:07:33

I might need to switch to stable at this point. Not having something automatically match my parens is completely disrupting my ability to write Clojure 😵

dave20:07:38

I think I was only on unstable because I wanted to get the floating windows early, back in the day. These days I'm not aware of anything on the unstable branch that I really want/need right now.

Noah Bogart20:07:58

It's odd that it happened at all. I wonder what changed on unstable that would do this.

dave20:07:02

The plot thickens! I installed Neovim stable, both 0.6.1 in the official Ubuntu stable PPA (that's a little out of date, but anyway...) and 0.7.0 which is the version you get with the Snap package, and parinfer still wasn't working in the same file I was editing. So at that point I realized that it probably wasn't the Neovim update that was the problem... I tried editing a different file, and parinfer is working fine. The content of this particular file must be confusing parinfer somehow.

dave20:07:09

I will say that overall, I have had very, very few issues running Neovim unstable. I would recommend it if you're on Ubuntu 20.04, since I observed today that the stable PPA isn't kept up to date with the latest stable release.

dave20:07:23

Maybe the 22.04 PPA is kept more up to date?

dave20:07:35

OK, I just found a legit corner case bug in parinfer. That was a fun ride. Creating an issue for that now.

🎉 1
dominicm20:07:41

Is it still maintained?

dave21:07:01

I don't have treesitter enabled

sheluchin21:07:32

Ah, ok. That rules that out 🙂

timo09:07:40

did you search for existing issues? @U0AHJUHJN I think this problem is known...

dave14:07:13

That does look related.

dave20:07:29

The last commit was 26 days ago, so I'm hopeful. 🤞