Fork me on GitHub
#spacemacs
<
2016-11-05
>
lvh02:11:45

I’ve just tried to get started with spacemacs

lvh02:11:47

using vim mode

lvh02:11:06

a lot of muscle memory is broken especially around paredit

eggsyntax02:11:49

ie you're used to paredit, and spacemacs' variant of it is disorienting?

eggsyntax02:11:38

You may want to see https://github.com/syl20bnr/spacemacs/issues/1812 — spacemacs author gives useful tip on how to make spacemacs use regular paredit.

lvh16:11:09

eggsyntax: so, e.g. I had C-k as hybrid-kill-sexp

lvh16:11:18

d$ is not, similarly, what I want

lvh16:11:34

those evil commands seem to be blissfully ignorant of sexps

eggsyntax16:11:15

@lvh SPC-k will show you most of the sexp-modifying commands that have a default keybinding.

eggsyntax16:11:21

Typing SPC-: will bring up a window where you can type partial commands by name & see what matches. Typing sexp there will bring up most of the other sexp-modifying commands, including ones that are not yet bound.

eggsyntax16:11:33

& of course you can establish a keybinding for any command you like.

eggsyntax16:11:57

I also sometimes use other vim commands rather than true sexp commands, eg da( to delete an sexp.

eggsyntax16:11:41

Note that calling a sexp-modifying command will leave you in evil-lisp-state, with a pink cursor, which means that you can type any of the other sexp-modifying commands without the SPC-k prefix, ie they’re available as single keystrokes. See here for more info on evil-lisp-state: http://spacemacs.org/doc/DOCUMENTATION#editing-lisp-code

eggsyntax16:11:20

Including sexp-navigation, eg once you’re in evil-lisp-state, H and L will navigate to previous/next sexp.

eggsyntax16:11:01

SPC-m (or, for me at least, ,) will bring up another set of commands having to do with evaluating sexps, sending them to a REPL, etc.

lvh19:11:25

Thanks! That’s very helpful 🙂