3 ms·
It isn't the first thing one sees upon starting vim for the first time, nor is it obvious in any other way.
by fnordfnordfnord 14y ago
It isn't the first thing one sees upon starting vim for the first time, nor is it obvious in any other way.
- freehunter 14y agoI could swear if you just ran the command "vi" rather than opening a file with vim it would load to a screen that shows you how to run the tutorial. I can't confirm that since I'm on a Windows machine at work right now, so I won't argue it. It does exist, but I'll acknowledge that it's not advertised heavily.
- fnordfnordfnord 14y agoI just freshly installed vi and tried that. Here's what I was greeted with. http://pastebin.com/HxvNP6Tr http://pastebin.com/HxvNP6Tr I've seen the tutorial that you're probably talking about a few years ago when I got curious about vi. It didn't really do it for me at the time. I'm prepared to believe that people willing to tolerate its ideosyncracies can be very productive in vi or vim. I've seen it first-hand. It also appears to be well suited to potentially reducing rsi-type problems. But it is not intuitive to learn nor is it the least bit friendly. That's a shame too because there is no good reason why it couldn't be so.