Oh, and I'll agree about vi. I learned just enough to get into mode, make the necessary changes, write out the new file and exit. I know it is far more capable and has a rich set of commands, but it's never been something I've spent time learning. I tend to use nano, and vi only if nano is not available on the (usually) SoC/embedded system I'm working on and needing to make configuration file changes.
(Score: 2, Insightful) by pTamok on Tuesday March 29 2022, @11:32AM (2 children)
Oh, and I'll agree about vi. I learned just enough to get into mode, make the necessary changes, write out the new file and exit. I know it is far more capable and has a rich set of commands, but it's never been something I've spent time learning. I tend to use nano, and vi only if nano is not available on the (usually) SoC/embedded system I'm working on and needing to make configuration file changes.
(Score: 1) by pTamok on Tuesday March 29 2022, @11:34AM
That should read "...get into [insert] mode..."
[Adding some extra text to batter my way through the lameness filter...]
(Score: 2) by maxwell demon on Wednesday March 30 2022, @06:27AM
I think vi is great for things like commit messages or other minimal edits. For everything else I use Emacs (actually, XEmacs).
The Tao of math: The numbers you can count are not the real numbers.