2 ms·
Confession: I use vi because when I was learning how to be a sysadmin (was already a coder) it was recommended -- back then (the '90s) you never knew if emacs w
by sabat 19y ago
Confession: I use vi because when I was learning how to be a sysadmin (was already a coder) it was recommended -- back then (the '90s) you never knew if emacs was going to be on a system, but vi was practically guaranteed.
I still barely know how to use it, though: my own fault. Laziness prevails. Some of the commands I use because I discovered them by accident (shift-C erases the rest of the line and puts you into edit mode -- I figured that one out because of a typo).
- kmt 19y agoDoes this mean that nowadays you can expect emacs to be installed on every system? From what I've seen, still no. So basic vi skills are still needed. But nowadays, there are many ways to avoid having to edit files with vi. If a system has sftp access you can mount it's file system via sshfs and edit files from your main machine in emacs. This way you could even have the files version controlled on your main machine. There's also tramp mode of course, but sshfs works better.
- LogicHoleFlaw 19y agoWhen you really need vi, you really need it. I'm talking about connecting to servers halfway around the world with the only access being via a serial connection. Straight-up serial console, none of this fancy newfangled terminal emulator nonsense. No amount of emacs and sshfs will help you then.