@jcsims: I’m actually planning to integrate that into Cursive, and allow it to use the Cursive internal APIs
Cursive wraps the IntelliJ APIs with a more Clojure-y interface
At least, the ones I use mainly
@cfleming: very cool. One of these weekends where I have some more time, I need to sit down and get comfortable with cursive
Has anyone combined spacemac with a clojure starter kit?
@colin.yates: not I, but the default clojure layer packaged with spacemacs is fairly decent
ah ok - I did a quick search for Clojure but nothing came up - installing it now.
@jballanc: where do I get that "default clojure layer"?
@sveri: you just have to add it to the layers in your .spacemacs
file
find the dotspacemacs/layers
function, then the dotspacemacs-configuration-layers
variable
just add clojure
to the list, and restart
@colin.yates: I haven’t done a 1-for-1 comparison, so I’m not sure if it has everything of the clojure starter kit, but it has at least cider and clojure-refactoring
@jballanc: bril - thanks.
@jballanc: thanks, that seems to work
note that the smartparens stuff is (mostly) under the “Lisp” section (`SPC-k`), everything else is under SPC-m
when you’re in a Clojure file
also, SPC-k
puts you into Spacemacs’ “Lisp” editing mode which is slightly disorienting at first
…still not sure if I’m crazy about it
I’ve been getting used to it and kind of like it.
my biggest gripe is that I usually am only doing 1 paren move at a time, and with the Lisp mode I now have extra effort to exit the mode once I’m done...
but maybe I’m just using smartparens wrong 😕
I still keep the smartparens key mapping up in a browser tab.
Took me a half-minute to realize it treats the code as a tree structure, heh.
I’m not a fan of the lisp-state
much bigger fan of smartparens/paredit
fyi, you can add evil-smartparens to clojure-mode/elisp-mode and then you won’t unbalance parens by using vim editing
(I actually removed lisp state cause I kept ending up in it)
Hmm. This is looking rather good.
@jcsims: Let me know if you have any questions - I’m planning to update the getting started doc very soon.
@colin.yates: I’m watching you
@cfleming (I’m ducking :))