4 ms·

I don't think a starter pack that completely disables the "Customize" interface would be a good candidate for default. https://github.com/hlissner/doom-emacs/b

I don't think a starter pack that completely disables the "Customize" interface would be a good candidate for default. https://github.com/hlissner/doom-emacs/blob/a2a5038b970df20ec512447b7bbbe96fa2446851/core/core-ui.el#L666 https://github.com/hlissner/doom-emacs/blob/a2a5038b970df20e... "Doom doesn't support `customize' and it never will. It's a clumsy interface" I find the Customize interface very useful.

dan-robertson 6y ago
Yeah, unfortunately doom isn’t designed to be beginner friendly. I’m personally in two minds about customize. It is quite clunky and I think it’s too easy to have your customisations overwritten by customise or something else or to have them overwritten in confusing ways. But it also gives a non-lisp interface to a lot of customisation (manually setting up the data structures can be a big pain to get right without it).
vfclists 6y ago
When you use the customize interface you sacrifice proper version control. Bad idea.
- grzm 6y ago
  You can include custom-file in version control easily enough.
Siira 6y ago
It's easier this way for a beginner. Things are consistent; You put `(setq foo bar)` in your config. It's very intuitive. (I have also lost some settings to customize's bugs in Spacemacs.)
- vvillena 6y ago
  And how do you arrive at the correct values for 'foo' and 'bar'?. The key feature of customize is discoverability.
lytefm 6y ago
I'd also say it's a good choice for beginners. Providing one way to configure things and explaining that reasonably well in tutorials and docs is fine. The only downside of Doom Emacs for a beginner like me is the non-standard package manager: Just following some packages docs for configuring isn't enough, it's also required to figure out when to execute that config code.