Fork me on GitHub
#vim
<
2021-06-03
>
Timofey Sitnikov11:06:23

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.

mamapitufo12:06:20

I'm thinking that maybe auto-pairs and vim-sexp were stepping on each other's toes?

walterl16:06:52

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.

Noah Bogart13:06:35

that’s very possible

mamapitufo14:06:27

yeah, looks like that was the problem... so far vim-sexp on clojure and auto-pairs in markdown and simple JS works fine 😁

grazfather14:06:01

Hm I didn’t know that vim supported importing native libraries

Noah Bogart15:06:41

what do you mean “import native libraries”?

noisesmith15:06:22

usually that means using plugins with machine code, instead of instructions for a hosted interpreter

👍 3
noisesmith15:06:49

which historically is rare (maybe not possible?) in vim

walterl16:06:52

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.

grazfather17:06:49

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