This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-10-25
Channels
- # aws (1)
- # beginners (6)
- # boot (403)
- # boulder-clojurians (1)
- # clojure (28)
- # clojure-china (1)
- # clojure-ecuador (2)
- # clojure-ukraine (2)
- # clojurescript (27)
- # clojurex (5)
- # core-async (7)
- # cursive (5)
- # datomic (4)
- # hoplon (160)
- # ldnclj (2)
- # ldnproclodo (2)
- # lein-figwheel (2)
- # om (182)
- # onyx (1)
- # re-frame (1)
- # reagent (40)
- # spacemacs (15)
could someone tell me how to configure it so that when I do an evil-lisp-state function, that I stay in normal mode, instead of staying in evil-lisp-state? Or help me understand why that’s the default and how to take advantage
@jeremyraines: i've been trying to learn more of the evil-lisp-state movements so that i'm more productive when i'm there
but i still move around mostly in normal mode, since that is still most intuitive
yeah. I know that the context-switch of changing modes is part of the point of this, but man the learning curve is rough
maybe the way to learn is just to always be in evil-lisp-state for clj
this is how i learned paredit, heh
yeah I might give that a shot. Doesn’t it give you smartparens bindings rather than paredit? and/or are they mostly the same?
also - how can I toggle that mode without performing a prefixed evil-lisp-mode function first? If I want to try toggling on off before just setting it for all clojure files
how familiar are you with elisp?
oh nvm, you can do Spc-: evil-lisp-state to turn it on
thanks
so you could do like (evil-leader/set-key "ol" 'evil-lisp-state)
hm, i will give this a go myself