This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-12-02
Channels
- # adventofcode (286)
- # aws (3)
- # beginners (243)
- # calva (4)
- # cider (51)
- # cljs-dev (8)
- # clojure (74)
- # clojure-conj (1)
- # clojure-france (1)
- # clojure-italy (1)
- # clojure-spec (21)
- # clojure-uk (22)
- # clojurescript (25)
- # clojurex (6)
- # code-reviews (5)
- # core-async (3)
- # cursive (1)
- # defnpodcast (1)
- # fulcro (29)
- # mount (1)
- # off-topic (85)
- # onyx (5)
- # other-languages (7)
- # pathom (6)
- # pedestal (6)
- # re-frame (20)
- # reagent (2)
- # reitit (8)
- # ring-swagger (10)
- # shadow-cljs (53)
- # spacemacs (8)
- # tools-deps (34)
SPC k
to enter the lisp state, b
for barf s
for slurp. j
moves to next closing boundary, k
moves to previous opening. I use evil-cleverparans which have a simple`>` and <
for slurp and barf respectively with no need for a state. It also has other movement keys that are all usable in movement mode with evil
I guess I will need to get used to lisp state. If I’m in insert vim mode, then esc + spc + k + s seem’s like a lot of work. Maybe I’m missing something.
you can try enabling safe structural editing with , T s
, then >
slurps and <
barfs
@U45J3R52L I did not know that evil cleverparens was already included.
it is, but it is hard to find and I also was wondering why this is not enabled by default…
I think mainly because evil-cleverparens has some confusing bindings for parens, curly brace, and brackets in movement mode that could be confusing.