Why, oh WHY, do those #?@ nutheads use vi?
Excellent article that explains my ardent devotion to an editor that hearkens back to days where visual terminals were luxuries.
(Originally spotted at JJLinuxLand)
Craig Maloney
More than you cared to know
1 user responded in this post
Subscribe to this post comment rss or trackback url
Echoes…
- I wonder if it's too soon to post that Coffee House Coders is on Wednesday, so as to get it on @lmorchard's radar.
- Corralary: If you've let your codebase get to the point where developers complain it's formatted wrong, fire your management.
- Managed to set the coffee pot this morning without putting water in it. Got a nice hot pot of nothing this morning for my trouble
- No problem. Sorry the response was late. :) LMK if you want any more recommendations. :)
- voted for "disagree"
Nearly everything he says is true for Emacs, except that there’s no insert mode.
The command to insert text in teco is ithis is my text$, where ‘$’ is how teco displays the escape character. That looks alot like vi. The odd thing is that Emacs stands for Extended MACroS. It was originally extended teco macros. And yet, vi owes history to ed.
I thought for a second that no comparison to Emacs would be made. There’s a jibe at the end. The learning curve graph is priceless.
Of course, i’m a long time Emacs and vi user. Emacs is primary, but vi is not foreign. So, the “I don’t know anyone who’s learned it that went back” is in error.