This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-06-03
Channels
- # announcements (1)
- # asami (13)
- # babashka (14)
- # beginners (58)
- # calva (49)
- # cljs-dev (6)
- # clojure (99)
- # clojure-europe (28)
- # clojure-gamedev (4)
- # clojure-nl (19)
- # clojure-spec (4)
- # clojure-uk (39)
- # clojured (5)
- # clojurescript (39)
- # code-reviews (3)
- # conjure (4)
- # cryogen (12)
- # cursive (21)
- # data-science (4)
- # datalog (1)
- # datomic (16)
- # duct (4)
- # events (1)
- # fulcro (6)
- # graalvm (1)
- # graphql (1)
- # jobs (13)
- # jobs-discuss (23)
- # kaocha (2)
- # lsp (15)
- # malli (24)
- # missionary (6)
- # off-topic (21)
- # polylith (75)
- # releases (2)
- # remote-jobs (4)
- # shadow-cljs (47)
- # sql (35)
- # vim (10)
- # xtdb (4)
I have been using https://github.com/eraserhd/parinfer-rust , it can take time to install because it requires Rust and friends but once working, it works very well.
I'm thinking that maybe auto-pairs and vim-sexp were stepping on each other's toes?
Weird. I use those two together and haven't noticed any problems. My only config for auto-pairs is the b:AutoPairs
setting above, and my vim-sexp config is just mappings.
that’s very possible
yeah, looks like that was the problem... so far vim-sexp on clojure and auto-pairs in markdown and simple JS works fine 😁
Hm I didn’t know that vim supported importing native libraries
what do you mean “import native libraries”?
usually that means using plugins with machine code, instead of instructions for a hosted interpreter
which historically is rare (maybe not possible?) in vim
Weird. I use those two together and haven't noticed any problems. My only config for auto-pairs is the b:AutoPairs
setting above, and my vim-sexp config is just mappings.
Yeah, but if it weren’t possible in Vim then all the calls to parinfer functionality would have to invoke a subprocess (like vim-fzf). I think that that would negate most of the perf benefits of the rust impleimentation