I actually started enabling it when writing other languages (Python/C++) to see if it could do its magic there.
It turns out I've been using smartparens without realizing--just opened a file and checked the active modes to find out.
The keys I've learned are (using evil):
- [Visual mode] S -> surround by a pair
- [Visual mode] d <char> -> delete pair of <char>
- [Visual mode] c <c1> <c2> -> replace pair of <c1> with pair of <c2>
Those along with C-M-k to kill a sexp and % to go to the other end of a pair have been all I need for my work (the vast majority C/C++ and Python).
One thing I keep putting off is figuring out a way to jump to the opening/closing quotes. For those I still have to go medieval if there's any nesting.
Both the advantage and disadvantage of lisp are its lack of structure and paredit forcing you to keep your code intact really prevents a ton of issues just by having it on.
The only paredit shortcut I know is M-s to remove a set of parens.
That said I also use boon, which has some modal editing in particular a way to skip past an entire set of parens.
To GP: Why not enable it just for sake of keeping your parens balanced. Make sure you have a good way to discover commands like selectrum. And tada. Don’t have to learn it all right away.
When I last tried this, I felt like I was struggling against the mode's understanding of my syntax, more than it was assisting me. I didn't figure out how to "think" in its language. I want to know if I'm missing out on something wonderful, or if it's more "just another tool, don't worry about it".