Follow

@mngrif Oh, sorry. Reading it again and I see your point.
vi is pretty complicated. it was invented by geeks for geeks centuries ago.
I love it but it taken years to be very good with vi. (I'm even using it as editor in my email client.)
That's the reason why - as default - is configured nano.
It is expected, that if you have a headless server, you are not beginner and nano is sufficient for you and vi is like king.

If you have an GUI system, then some default text editor you have installed by default either by Gnome, KDE, or any other lightweight GUI system. You should be never without simple text editor - still sufficient for editing simple configuration files.

If you are editing complicated configuration file, then - again - you are either very skilled and nano/vi is sufficient for you or you should install some nifty editor full of features (but usually with huge list of library dependencies and the size of the package).

My experience - as working with Unix over 25 years - is that more skilled admin is, he is working more with vi/nano/emacs.

But I have to warn you, emacs is for real geeks. It's like operating system inside your operating system. I expect that there is some macro/plugin to emacs capable to control your coffee-machine.

When you take it from other side - what editor is installed by default on Windows fulfilling your requirements?

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.