This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-01-13
Channels
- # aleph (1)
- # announcements (14)
- # aws (8)
- # babashka (3)
- # beginners (49)
- # cider (6)
- # clara (7)
- # clj-kondo (58)
- # cljs-dev (17)
- # clojure (65)
- # clojure-dev (45)
- # clojure-europe (5)
- # clojure-italy (4)
- # clojure-nl (25)
- # clojure-norway (3)
- # clojure-uk (68)
- # clojurescript (10)
- # cursive (5)
- # datomic (12)
- # emacs (24)
- # fulcro (149)
- # hoplon (56)
- # kaocha (2)
- # luminus (18)
- # malli (7)
- # off-topic (12)
- # other-languages (82)
- # reagent (16)
- # reitit (7)
- # shadow-cljs (44)
- # spacemacs (4)
- # tools-deps (48)
- # xtdb (17)
If anyone is using Windows here:
https://twitter.com/borkdude/status/1216667224355811328
@kevin.van.rooijen I'm using lispy a bit now, but when I write
(fn [])
the [
triggers lispy-backwards
so it's impossible to write []
. Do I need to activate some specific clojure mode?
I use this:
(evil-define-key 'insert lispy-mode-map
"[" #'lispy-brackets-or-barf)
(evil-define-key 'insert lispy-mode-map
"]" #'lispy-slurp)
I believe something like this?
(define-key lispy-mode-map "[" 'lispy-brackets-or-barf)
(define-key lispy-mode-map "]" 'lispy-slurp)
hmm, that gives me Wrong type argument: commandp, lispy-brackets-or-barf
when I try to use it.
I must be missing something, lispy has done a lot of work to be compatible with clojure, but the behaviour I'm seeing would make it unusable..