This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-11-18
Channels
- # announcements (2)
- # babashka (65)
- # beginners (104)
- # boot (8)
- # calva (23)
- # circleci (3)
- # clj-commons (1)
- # clj-on-windows (3)
- # clojure (43)
- # clojure-europe (45)
- # clojure-france (2)
- # clojure-italy (3)
- # clojure-nl (3)
- # clojure-norway (13)
- # clojure-uk (4)
- # clojurescript (5)
- # core-typed (2)
- # cursive (5)
- # data-science (2)
- # datalevin (10)
- # emacs (38)
- # events (2)
- # fulcro (11)
- # graphql (6)
- # gratitude (2)
- # helix (11)
- # hugsql (3)
- # jobs (2)
- # lsp (17)
- # luminus (1)
- # malli (15)
- # missionary (3)
- # nrepl (6)
- # off-topic (6)
- # pedestal (2)
- # portal (16)
- # reagent (33)
- # reitit (4)
- # releases (12)
- # ring (2)
- # sci (3)
- # shadow-cljs (21)
- # spacemacs (7)
- # sql (5)
- # tools-build (36)
- # web-security (2)
What are the modern init.el
/config starter setups for experienced Clojure devs looking to get in to emacs for the first time? (I remember this being discussed on a clojure podcast in the last year or so but can't find the source)
I think the simplest would be a tiny single file setup - e.g. something like mine https://github.com/bbatsov/emacs.d/blob/master/init.el
Prelude (https://github.com/bbatsov/prelude/) is also fairly simple compared to most of the competition and for obvious reasons it works well for Clojure development. 🙂
From mine and other users' experience I found that spacemacs's abstraction model is good
It doesn't require deep familiarity with emacs to get going, but it doesn't stop you or hide anything from you
Well, if it's simple for you I can't argue with that. I've just always been on the minimalist side of everything and avoid additional abstractions when possible.
Abstractions have a price, but sometimes we're willing to pay it because they free us from worrying about the little things
It's been my experience that Spacemacs gets out of my way while Doom Emacs forces the user to contend with it constantly
I don't dislike abstractions in general; I'm just wary of abusing them. I've yet to see some real problem that Spacemacs layers have solved, yet they introduce a mental overhead as you have to learn them to use them. Adding abstrations doesn't necessarily make something "simple" (Clojure). Something they make something "easy and complex", and sometimes it's even worse. 🙂
That's super subjective, of course, and I encourage everyone to just stick with whatever works for them.
If you wish to use Spacemacs, this guide may be of interest https://practical.li/spacemacs/install-spacemacs/
Gotta say, I can’t live without lisp interaction mode in spacemacs; SPC k
. @U05254DQM’s guide is awesome. I actually started with https://youtu.be/NDrpclY54E0 by him.
Gives just enough of an intro to using spacemacs with Clojure.
Also, Spacemacs: Easy? Yes. Simple? …not really, definitely not simple under the hood.
If you do decide to go raw-emacs, figure out how to hook up melpa, then get which-key
to show keybindings and evil-mode
for vim emulation (I think we can all agree the default emacs bindings absolutely http://xahlee.info/emacs/emacs/emacs_pinky.html).
I don't know these other modes well enough to know whether I am even more minimal than they are, but I suspect I am: clojure-mode only 🙂
After not doing much programming for a long while and I had to pick up emacs again when I started hacking again, I used Spacemacs for a long while which I liked for a long while. Finally got fed up with not being able to understand what was going on for various modes that I had problems with. Been trying Doom which was a bit simpler. But now I’ve decided all the evil stuff really gets in the way in both Spacemacs and Doom (I don’t use any of it, I use them in holy mode and most documentation for Spacemacs/Doom show the evil way) Both were nice when they worked, but if something didn’t work, it was hard. It was hard for me to stay in sync with my colleagues who were running their own (heavily customized) emacs. So I’m going to try Prelude (again, used it when it first came out). But if you need to use evil mode, they are both nice for that.
Anybody use the https://www.neilvandyke.org/sicp-texi/? I’m trying to unzip it, but gzip gives me an error.
$ gzip -d sicp.info.gz
gzip: sicp.info.gz: not in gzip format
https://sarabander.github.io/sicp/html/index.xhtml This HTML version is IMO the nicest (I prefer to stay as far away from TeX/LaTeX as I can)
I'd try tar xf
on that file though
I've used eww
in the past and it's worked fine, but you might also be able to use the EPUB format with something like nov.el
https://github.com/sarabander/sicp
Interesting… Seems like it wasn’t compressed at all.
$ file sicp.info.gz
sicp.info.gz: data
$ file -I sicp.info.gz sicp.info.gz: application/octet-stream; charset=binary
Also, when I cat
it out, it just prints it like there’s nothing wrong. Like it isn’t garbled, just plaintext.
How did you download it? Most likely your browser was trying to be helpful, and uncompressed it
❯ wget
...
❯ file sicp.info.gz
sicp.info.gz: gzip compressed data, was "", last modified: Wed Jan 10 09:29:09 2007, max compression, from Unix, original size modulo 2^32 1487932
The browser did in fact decompress it. I wonder why it didn’t take off the .gz
extension.
Browsers support gzip so that web pages can be sent in a compressed format (identified by the content type header). But they also tend to believe the filename claimed by the server, and in this case your browser wasn't smart enough to put two and two together. I wonder if some browsers handle this better than others. I know I've seen it happen with Firefox, but don't recall seeing it with Chrome.