pclissold wrote:
unixfool wrote:
The better way, IMO, would be to learn how to minimally use vi.
You are, of course, entitled to your opinion. However, I for one would rather stick needles in my eyes than use vi. Despite all his good work, Bill Joy has a special place in Hell reserved for him, all because of vi.
Let the editor wars begin.
I never said I liked vi. You're not understanding things.
If your boss told you to log into a box to fix something and you had to rely on vi (and nothing else) to edit some files, you'd be in trouble. Would you go back to your boss and say, "I can't edit the files to fix the issue because I don't know how to use vi."? Would you spend extra time trying to get another editor onto the box so that you could then fix the issue? If so, your assigned task will be sidelined.
Why even let a situation like that happen. It takes memorizing all of 2-3 keystroke combinations to know how to edit a file using vi.
It is easier to just learn those few keystrokes than have to ensure you have access to your favorite editor so that you can get trivial file edits done. No matter your feelings of editor X, you would be more productive if you tried to learn basic operation of editor X instead of avoiding editor X.*
This has nothing to do with favoritism or editor warring. It just makes sense to me to empower myself to at least know how to use it. A good example: I hated Cisco PIX and still do, but at least I know how to perform basic commands/troubleshooting/maintenance on them...had to force myself to learn it, but I have to ask for less and less help now and I can troubleshoot and conduct maintenance way faster now.
* - X represents your least favorite editor (doesn't have to be vi).