I use Emacs, vi, nedit, and sometimes good ol' ed. Whatever is most appropriate, and available under the circumstances.
Today's Helpful Hint: When your company server won't boot because of problems in /etc/fstab, you can't get fsck to act sanely, and you're in a single-user shell with your boss staring at you -- even vi is not available -- use ed. Growing up with a line editor in the 70's has saved my butt more than once.
When your company server won't boot because of problems in /etc/fstab, you can't get fsck to act sanely, and you're in a single-user shell with your boss staring at you -- even vi is not available -- use ed.
In upper division college, I was finally off of the System 7 PDP and on the CS VAX which had vi available and ... I couldn't use it most of the time because it was too slow, so I still used ed.
But, question ... how do you edit files using only /bin/sh if for some reason ed isn't available? I figured it out under fire when I was trying to get a Microport install working until I established that it didn't have drivers for the hard disk for the machine.
sed