3 ms·
I guess ParEdit has staying power, but isn't Smartparens[+] the way to go these days? https://github.com/Fuco1/smartparens https://github.com/Fuco1/smartparens
by michaelsbradley 9y ago
I guess ParEdit has staying power, but isn't Smartparens[+] the way to go these days?
https://github.com/Fuco1/smartparens https://github.com/Fuco1/smartparens
- meken 9y agoYMMV but for what it's worth I became frustrated with smartparens when I couldn't figure out how to do something very simple. I think it was traversing down into the next sexp. I got different behavior when my cursor was right up against the sexp versus one space before. Also whereas paredit really pushes me to have a mental model that the lisp source code forms a tree (e.g. up, down, left, and right being the main operations), I found smartparens drove my mental model back to treating the code a string of characters.
- michaelsbradley 9y agoInteresting. I wonder if it has to do default settings, or something like that. I'm using bbatsov/prelude[+], for several years now, and Smartparens (per prelude's config) has always behaved for me like a better ParEdit. [+] https://github.com/bbatsov/prelude https://github.com/bbatsov/prelude
- meken 9y agoAh thanks for the recommendation. For what it's worth I was using the evil-mode smartparens layer bundled with spacemacs.
- open_bear 9y agoParinfer is another good attempt at making editing Lisp code easier: https://github.com/shaunlebron/parinfer https://github.com/shaunlebron/parinfer