How much time have you wasted on configuring Emacs or Vim to the point where everything works according to your wishes? You could have saved that time by using gedit or VSCodium. In exchange for less "perfection", you could have gotten more work done by avoiding Emacs and Vim.
Perhaps you should use MicroEmacs or nvi instead.
Vim. In fact not much time, because I don't have much wishes. I just want vim to compile and run programs properly.
However I spent a lot of time learning how to use vim efficiently, but that's worthwhile.
For Emacs, after initial configuration, not that much at all.
I only fiddle with the configuration when I want to add new packages that I find interesting or useful, which, thanks to use-package, is a very simple and straightforward process that usually involves adding one or two lines (per package) to the configuration file.
The majority of my time is spent using Emacs on various tasks, both personal and professional.
There are no better editors than Emacs for the type of programming that I do. Nothing offers something even close to SLIME/Sly for example. While I share your dislike for those who spend all their time customizing their setup, Emacs is genuinely more productive for me than the other options.
I don't even remember when I had to touch my init.el the last time.
Vis. I worked through the vimtutor a while back, and over the years I've picked up a few tricks.
I used plan9's acme for a couple months recently, it really showed me how little you need from an editor to be productive. It has no config file, and few command-line launch options. This is nice, because it has relatively sane defaults and stops you from spending hours fucking around with your init.el or .vimrc files. It has some drawbacks though, not being able to turn on line numbers can be a nightmare when working through a stack trace.
The best thing about acme though is the command window where you can call unix commands (with options) really easily, which absolutely BTFOs dedicated editor packages.
There are some quirks with acme though such as common keyboard shortcuts not working, being unable to select text larger than your screen size with the mouse, and the aforementioned lack of line numbers. I alternate between vscodium and vim now, but acme really shows how less is more when it comes to text editors.
not being able to turn on line numbers can be a nightmare when working through a stack trace.
Not being able to hit "Enter" on a stacktrace entry and get to the specific line can be a nightmare when working through a stack trace.
ma using komodo
yes i eat shit
I get very frustrated trying to program EMACS, the code is too byzantine to live up to their ideals of programmer control.
>>10
Switch to MicroEmacs (mg), where you won't have to waste time in programming the text editor itself. Get to work immediately.
Thank you friend but I will build my own editor in MIT SCHEME and it will bring truth and salvation to the world.
I will build my own editor in MIT SCHEME
What's wrong with EDWIN?
EDWIN suffers many of the same defects as EMACS.
For example, its PAREDIT relies on regex to navigate parenthesis taking O(n) time. This is a consequence of the text buffer being too inflexible for a programmer to make the necessary additions for an optimal O(log(n)) algorithm.
This and other such shortcomings make for very difficult and contrived programming.
nvi
Too bad it doesn't implement Lisp mode.
This option is not yet implemented.
I get very frustrated trying to program EMACS
You do not program EMACS. EMACS programs you.
You do not change EMACS. EMACS changes you.