This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # 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)
- # crux (17)
- # cursive (5)
- # datomic (12)
- # emacs (41)
- # 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)
Yes, I have used Spacemacs for Clojure development for over 3 years now. It's really increased my productivity. It also stopped me wasting days and weeks (years) massaging my init.el file.
There is very little config needed thanks to the layers, actually you can get Spacemacs to do it all as it will prompt you to add layers when you open certain file types.
You can of course customise Spacemacs as much as you want.
Another great thing is the community of contributors to Spacemacs (I am one too). As it's a community effort, then you get to use lots of other people's skills. I have used one person's config previously, but that does risk them abandoning the project.
There is also a #spacemacs channel here and I also am writing a book (with Screencasts) on Clojure development with Spacemacs
The most important advice, use the Spacemacs
develop branch rather than the default master branch.
develop is very stable and has been for the last 2 years or more.
spacemacs did more and had more layers of integration. unfortunately that meant it broke a lot and I was always scared of upgrading. with doom I get 95% of what I cared about and don't have all the fear
@corasaurus-hex Do you use paredit when editing lispy stuff with Doom? I couldnt get it to work as nicely as spacemacs and still using it as I found doing clojure on spacemacs involves less config than Doom.
I can share when I'm back at my computer, but I don't tweak paredit at all. I'm interested in what spacemacs does to make paredit nicer
Isn’t slurp/barf just
> on the opening /closing? Or is it evil-cleverparens?
looks like it is cleverparens: https://github.com/luxbock/evil-cleverparens#slurping-and-barfing
I have both enabled, but I guess I’m only using the cleverparens bindings (also using doom emacs myself)
> it’s good but doom emacs is better imo
Spacemacs community is huge (in relative terms). And they keep adding/improving things all the time. That means that things do break from time to time. But that doesn’t mean that Spacemacs is unstable. You absolutely can make your config stable and solid and upgrade with no fear.
You just need to follow a few rules, the rules you should follow with any kind of configuration, be that Prelude, Doom, Spacemacs or anything else - you need to be cognizant about what you’re adding to it. Don’t add layers and packages without first studying them, learn what layer includes, see if you need those packages, ignore those that you won’t be using, avoid the bloat, minimize conflicts.
I currently have over 300 packages installed. In the past three years I had only two or three times when after pulling the latest of Spacemacs things broke and it took me longer than ten minutes to figure out what the heck. Most of the time things break because of some upstream change - when a package that has some tighter integration gets an update. That’s not Spacemacs’s fault, but it needs to be fixed for that package. Exactly because of that it is recommended to use
develop branch of Spacemacs, because things like that get fixed very fast.
If you’re not using Spacemacs, you may feel FOMOed. With Spacemacs sometimes you may feel overwhelmed.
Overall - I’d recommend anyone (beginner or an Emacs-Jedi) to at least try Spacemacs. For a beginner it increases visibility of things - hidden gems of Emacs are there on the surface, waiting for you to be discovered. For a seasoned Emacsen it offers a lot of good stuff as well.
and when things broke I didn't get much help anywhere with spacemacs. whereas the doom discord is super active and the doom maintainer is quick to help and fix issues.
i haven't used doom emacs as much as Nate Sutton, but so far my experience has been similar (i tried spacemacs first -- more than once). the doom maintainer was also helpful when i got stuck initially. i agree in general it's worth trying both though. what i did find helpful was plexus' chemacs -- that allowed me to use more than one version of emacs, so i could fall back on what i was more comfortable with.
Spacemacs is horribly bloated with weird abstractions and indirections, and it's concrete.
I'm definitely tempted to just wipe all the keybinds full stop and only bind commands I use often, but I don't want to lose the discoverability
Yeah that's the issue. I'd like to discard the cruft so I can make everything shorter and reduce the surface area I have to think about, but I don't want to have to chase rabbits.
This is the diff I needed to expose the
'visual line numbers option that was added to native Emacs. In a normal init file, this would be one line,
(setq display-line-numbers 'visual), I had to navigate through 4-5 levels of indirection and basically restate Emacs' own documentation to get it merged. Totalled +58 -15