It would be nice if that table included the full versions of some of the commands. For example:
:sp is equivalent to :split
:vs is equivalent to :vsplit
For me at least, the abbreviated commands become more intuitive if I know exactly what's being abbreviated (most of the time I type :vsplit instead of :vs anyway).
Probably "regular" vim goes last in that list because the author assumes Windows users are unfamiliar with the terminal. But it can be easier to open vim in the console for something quick or if you're doing something over the network (say, ssh). For example, I use the terminal often for quick commit messages or short edits and consistently for Mutt. Regular vim is easier with Mutt rather than kicking open G/Mvim and then returning to the terminal to send the mail. (You can automate the right return to focus for the terminal when you close G/Mvim, but it's still a bit jarring.) For very long edits on a good connection, I will open sshfs and use M/Gvim, but in general ssh + vim is simpler.
[+] [-] nitrogen|15 years ago|reply
[+] [-] sigzero|15 years ago|reply
[+] [-] koenigdavidmj|15 years ago|reply
A lot of his keybindings are are similarly nonstandard.
[+] [-] nitrogen|15 years ago|reply
[+] [-] BoppreH|15 years ago|reply
[+] [-] alexkay|15 years ago|reply
[+] [-] ssx|15 years ago|reply
[+] [-] Vitaly|15 years ago|reply
[+] [-] epistemenical|15 years ago|reply
What advantage does console vim have over gvim
[+] [-] telemachos|15 years ago|reply
[+] [-] jamesbritt|15 years ago|reply
[+] [-] jimmyjim|15 years ago|reply
[+] [-] crazydiamond|15 years ago|reply
There's also a ruby gem named "cheat" which has cheatsheets for 100's of commands and programs. you can access them on your command-line.