"Your problem with vim is that you do not grok vi".
Yes, that StackOverflow answer (which starts with the above line) is one of the best I have ever read, on any subject, not just vim.
(However, I should mention that I have not read, say, thousands of stack overflow answers, only in the range of hundreds, because I was never a heavy StackOverflow or StackExchange user.)
Anyway, FWIW, I think that answer could described as partly explaining the "Zen" of vi(m).
And for people who are intrigued by the benefits of vi(m) mentioned by various commenters in this thread, and would like to start using it, I have a small vi tutorial, which is applicable to vim too.
Those new to vi(m), check this vi quickstart tutorial that I created.
From the start of a Twitter subthread I wrote about the tutorial (thread unfortunately deleted later by accident - Twitter should have an undo feature like vim, heh):
[ Those new to vi / vim, hit the ground running with my short vi quickstart tutorial here:
I first wrote that tutorial at the request of a couple of Windows system admin friends of mine (at a company where I worked earlier), who were tasked with managing a few Unix boxes, without knowing Unix. They used the tutorial and later told me that it helped them to quickly start using vi to do their work on those boxes, including editing config files, simple shell scripts, etc.
Edit: Since vi is mostly a subset of vim, the tutorial works for vim too. ]
Yes, that StackOverflow answer (which starts with the above line) is one of the best I have ever read, on any subject, not just vim.
(However, I should mention that I have not read, say, thousands of stack overflow answers, only in the range of hundreds, because I was never a heavy StackOverflow or StackExchange user.)
Anyway, FWIW, I think that answer could described as partly explaining the "Zen" of vi(m).
And for people who are intrigued by the benefits of vi(m) mentioned by various commenters in this thread, and would like to start using it, I have a small vi tutorial, which is applicable to vim too.
Those new to vi(m), check this vi quickstart tutorial that I created.
https://gumroad.com/l/vi_quick
From the start of a Twitter subthread I wrote about the tutorial (thread unfortunately deleted later by accident - Twitter should have an undo feature like vim, heh):
[ Those new to vi / vim, hit the ground running with my short vi quickstart tutorial here:
https://gumroad.com/l/vi_quick
I first wrote that tutorial at the request of a couple of Windows system admin friends of mine (at a company where I worked earlier), who were tasked with managing a few Unix boxes, without knowing Unix. They used the tutorial and later told me that it helped them to quickly start using vi to do their work on those boxes, including editing config files, simple shell scripts, etc.
Edit: Since vi is mostly a subset of vim, the tutorial works for vim too. ]