5 ms·
M-x customize exists since forever, and is more plug-and-play than VSCode ever was. The real problem with Emacs is the shitload of bugs that case weird, undocu
by otabdeveloper4 3y ago
M-x customize exists since forever, and is more plug-and-play than VSCode ever was.
The real problem with Emacs is the shitload of bugs that case weird, undocumented and annoying behavior. A scripting language like elips is not meant for programming something as large and complex as Emacs.
- hollerith 3y agoI dislike customize though whereas I like the GUI interface to settings in vscode. I agree Emacs has too many bugs (but I haven't found anything that suits me better for maintaining notes and to-do lists and such).
- _a_a_a_ 3y agoI've found very few in many years' use. You may be a more competent user than I. Please report bugs, the devs are very responsive.
- precompute 3y ago> The real problem with Emacs is the shitload of bugs that case weird, undocumented and annoying behavior. Could you name a few of these "bugs"? I use Emacs for practically everything and bugs are very difficult to encounter, even on Emacs HEAD. > A scripting language like elips is not meant for programming something as large and complex as Emacs. Well, that's just plain wrong. A lot of vanilla Emacs functionality is written in Elisp.
- otabdeveloper4 3y agoCore Emacs is simple enough to mostly be bug-free. But any elisp package will have lots of annoying small day-to-day bugs and glitches.
- precompute 3y ago> But any elisp package will have lots of annoying small day-to-day bugs and glitches. I disagree. That's a broad and false generalization. Most packages are bug-free. If you're submitting to MELPA you need to make sure your package works and follows some guidelines for namespaces and organization, which can all the checked within emacs itself. Every package on a package tracker is vetted by at least one external dev. Emacs functions usually require little to no modification for years, because the core is very stable.