3 ms·
> I don't even want to spend 45 mins a month fiddling with config. I really don't understand Emacs people. Some people like to customize their environment to t
by outworlder 4y ago
> I don't even want to spend 45 mins a month fiddling with config. I really don't understand Emacs people.
Some people like to customize their environment to their exact specifications. Others will use whatever is available and never change it.
That is not required. Although default Emacs is pretty barebones (from a modern interface standpoint, not features) one can get a pretty good kickstart by using something like Spacemacs or Doom emacs and only sprinkling a bit of configuration here and there.
I too had a pile of config accrued over years - mostly porting features from other editors to Emacs. After adding Doom, I have just a few lines, it does all the rest.
The point is - usually on other editors you need to either wait for someone to create a "plugin" to do what you need, or you need to create a full blown plugin yourself, which is not a small task. In Emacs, it's extremely easy to create functions that will do tasks for you. And that gets addictive.
- enbugger 4y ago>or you need to create a full blown plugin yourself, which is not a small task That is what I thought when was motivating myself to continue diving into vim and emacs. In the end it turned out that the this this problem of "difficult extensibility" exists only in my head but not in VSCode or IntelliJ IDEA. Eventually, you can do magic on your files with sed/python/any other language in terminal and this most likely is better solution because it is editor-agnostic and good for automation.