This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-07-18
Channels
- # announcements (4)
- # aws (24)
- # babashka (118)
- # babashka-sci-dev (18)
- # beginners (56)
- # calva (2)
- # clojure (54)
- # clojure-dev (8)
- # clojure-europe (25)
- # clojure-gamedev (5)
- # clojure-nl (1)
- # clojure-norway (6)
- # clojure-uk (2)
- # conjure (1)
- # core-async (1)
- # data-science (3)
- # datomic (5)
- # emacs (8)
- # fulcro (4)
- # hyperfiddle (12)
- # interop (1)
- # jackdaw (4)
- # lsp (5)
- # mid-cities-meetup (5)
- # nbb (32)
- # off-topic (21)
- # reitit (5)
- # shadow-cljs (12)
- # sql (8)
- # vim (18)
- # xtdb (9)
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 😵
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.
It's odd that it happened at all. I wonder what changed on unstable that would do this.
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.
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.
OK, I just found a legit corner case bug in parinfer. That was a fun ride. Creating an issue for that now.
It might be related to this https://clojurians.slack.com/archives/C0DF8R51A/p1653747932108769?thread_ts=1653738137.277979&cid=C0DF8R51A.
did you search for existing issues? @U0AHJUHJN I think this problem is known...