Hacker News Reader

Comment by noelwelsh | Hacker News Reader

At some point I realised maintaining my own Emacs setup was just too much work. I've used a few Emacs setups (Prelude and Spacemacs are the ones I used for the longest) and now I use Doom: https://github.com/hlissner/doom-emacs It's very fast and has a lot of built-in in niceties, and I find it easier to understand than Spacemacs.

If you use Doom make sure to use the develop branch.

View on HN

Oh man, your link led me to shackle[1] to make transient buffers behave and I have wanted that for... well for as long as I've been using Emacs really, and that's quite a long time now. I don't get how anybody is fine with Emacs' default "let's pop this buffer anywhere, possibly hiding a useful window".

[1] https://github.com/wasamasa/shackle

That looks awesome.

Emacs's default behavior in this respect is theoretically customizable, but the mechanism for doing so (display-buffer-alist) is (to me) incomprehensible. It seems like what Shackle does is provide a clean interface for specifying rules that get translated into display-buffer-alist rules.

Yeah I've tried a few time to customize this behavior over the years and while I did manage to improve it somewhat it's still far from how I'd like it to be.

I agree. Doom takes the best of emacs and vim and mashes them together nicely. I've been using it for more than a year and haven't looked back.

There is a challenge configuring your version of Doom, but the project's Discord channel is active, friendly and helpful.

doom-emacs looks very nice, but development stopped on January? There is an "development" branch, which is ~4000 commits ahead from master. The documentation suggests fetching the master branch, so whats the deal here?

Use the develop branch. It hasn't been merged into master because of long running reworking, but I don't follow Doom closely enough to know all the details.

Master is almost 4000 commits behind but zero commits ahead after almost a year so simply shouldn't exist.

Multiple eternal branches are pointless and need to stop.

Go tell the core developers...

What part of your setup was taking a lot of time to maintain ? I find that once I configured something I rarely need to change it. There are some packages that tend to break existing configurations when updated, but that is not something that I do regularly.

There are new packages coming out that are really useful but I'm not going to find out about them on my own. For instance, I didn't know about helm until I started using Spacemacs.

That README feels like it's aimed explicitly at me. Maybe it's time to try it out

Reply on news.ycombinator.com