Re bracket highlighting. I use Clojure Warrior and disable vscode's built-in one.

I use bracket-pair-colorizer-2 and also disable the built-in one

It would rock to have a clojure user vscode wiki or such with all these little suggestions :)

@pez Which setting is it to disable vs-code built in one?

@jeremy642 https://stackoverflow.com/questions/45301283/how-to-disable-angle-bracket-highlighting-in-visual-studio-code

Thanks

That looks much nicer.

I would definitely suggest swapping in one of the above paren matchers

My issue was really that VSCode's paren matching is inconsistent, but perfectly acceptable in a language like typescript etc. I go mad in lisp without some support ;)

As I see it, most languages don't find so many adjacent parens regularly. Leftmost matching is definitely better when this happens, but Microsoft has never catered to a large community of Lisp hackers before, so vscode is not very adept yet :)

I rebound a bunch of paredit keys recently and am finding myself missing parinfer less

particularly am finding the paredit navigation stuff more useful and using vscode's goto matching pair less

I have also rebound many paredit keys. The default ones are pretty lame.

I really love the thought that has gone into Parinfer, but Paredit works really well once it clicks.

My issue with Parinfer is that it folds the trailing parens. It shouldn’t need to and then it would be compatible with calva-fmt.

I don’t utilize paredit enough. I haven’t gotten comfortable with it and I kept switching ides a lot so my keybindings kept changing where i’d familiarize myself with something different like smart parents.

I bound transpose to ctrl-alt-t, rebound splice to ctrl-alt-m, and split to ctrl-alt-/

I use a programmable keyboard with the arrows on a layer at s/e/d/f and so this also puts transpose logically near my navigation keys

and splice/split near slurp/barf

my only real gripe now is that you can't slurp from more than one layer deep

like you can in emacs