Jay BosamiyaCurrently playing around with switching my #Emacs config from a hand written multi-thousand LoC pile of code I’ve grown and maintained over the past 6-7 years to a much shorter thing, using #DoomEmacs as a foundation. Overall I quite like Doom Emacs’s style but I’m also surprised at some of its defaults, so it might take me some time to make a complete switch, as I find places it departs from vanilla Emacs and I want those settings reset. Also I don’t know how stable depending on Doom Emacs will be, given my particular preferences, so might end up switching back to my old config that gives me way more control anyways.
Steven Braun@jaybosamiya which defaults are you surprised about?
@sbraun I'm still discovering more as I use it; most of it easy to change/update/reset, so am not complaining. Just surprised by it.
Also, to preface this, I am not an evil-mode user, and prefer regular Emacs bindings.
Current list:
1. `+default-want-RET-continue-comments`
2. C-a and C-e not behaving as they would on Vanilla emacs
3. tab-always-indent behavior: I quite like the Emacs default of reindenting from anywhere on the line (i.e., `t`). I can understand why this default was changed though, but I am surprised it is changed to `nil` rather than `complete` which might make more sense for newcomers.
4. smartparens on by default: I don't quite care for it; there is a `+smartparens` in `init.el`, but removing it doesn't disable it (instead just disables some configuration of it). Actually disabling it requires setting up a hook (I later found out that the FAQ does have instructions for this, but if it needed an FAQ, maybe there should've been something easily toggleable, or at least a pointer to the FAQ for newcomers?)
5. undo changed: I find vanilla emacs's undo more powerful, and for newcomers I'd be surprised if they'd ever even find or realize that undo can be more powerful. I know vanilla undo is a tiny bit surprising for folks, but imho that lasts only for a short while before realizing how useful it really is.
6. `~` in IDO being unnecessarily bound, making typing `C-x C-f ~/foo` not work as expected. IDO already has support for `~/`, so I am not sure why `~` is being bound the way it is.