> my wife
> vim user
fake
Look, some of us old farts started on Linux back before nano was included by default, and your options for text editing on the command line were either:
- vi/vim, a perfectly competent text editor with arcane and unintuitive key combos for commands
- emacs, a ludicrously overcomplicated kitchen-sink program that had reasonable text-editing functionality wedged in between the universal woodchuck remote control and the birdcall translation system
Given those options, most of us chose to learn how to key-chord our way around vim, and old habits die hard.
:q!
I’m sorry, you need to :s/replace/her/ as soon as possible.
I refuse to see how vim and emacs is worth learning. I only use it because that’s the only option when editing server files. Beyond this, I couldn’t imagine coding in these environments from scratch.
By the way, for editing server files consider nano. It’s also widely available, has simpler shortcuts and displays them on the screen. It’s obviously not powerful like vim, but a good match when you just need to edit a config file.
Nano is just as fiddly as vim and way less powerful when you actually figure out what you’re doing though?
Ie a completely redundant piece of software that has no place being pre-installed anywhere
I only use it because that’s the only option when editing server files.
suggestion 1: use nano. Unlike vi(m) and emacs, it’s meant for humans, all the command shortcuts you can execute are listed at the bottom.
suggestion 2: browse the servers in question via your file explorer (sftp://user@server or just sftp://server) of choice or WinSCP if you’re on windows, open whatever file with your local graphical text editor of choice.
Nano is perfectly fine for me.
But I know the basics of vim if I need to use it.
