I've decided to jump into the cold water and purge every IDE/Text editor except for VIM.

Let's see how this will work out :).

@nergal No backup, just vim. I do have gawk and sed because some of my bash scripts use them :).

@Ghosty I have been learning emacs. Turns out to be simpler than vim. Who knew?! Not to mention, I am now of the mind that once documentation exceeds more than one manual page, texinfo is an upgrade option one should consider. Would not have to write many manual pages and then concatenate to <term>-all or write a <term>.directives. See systemd.directives(7), ffmpeg-all(1).


@nergal @Ghosty one nice thing about Emacs, if you don't like the keyset or the stateless (modeled) editing, you can install Evil mode and voila everything you knew before works. I use them both. I just feel wrong doing Lisp in vim, and nothing ng can do syntactical indentation of Lisp like Emacs, because it understands it internally. Love them both.

@Absinthe @Ghosty it was common consensus that emacs was resource-hungry. *vi? was lighter. Then atom, sublime-text and visual studio code entered the picture. I tried them and they were too much. Emacs has been here for over 4 decades. It is quite healthy now!

@nergal @Absinthe The modern and mostly Electron based code editors are really resource hungry. I used to use VS codium out of convenience. But I don't like it's mentality. It tries to be everything. I swear with some configuration I could set up VS codium to replace every tool I use on my Linux setup.

I prefer the idea that one program solves one or at least a small amount problems and not all of them at once :).

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves. A STEM-oriented instance.

No hate, No censorship. Be kind, be respectful

We federate with all servers: we don't block any servers.