Earlier quoted context omitted.
Definitely don't let this discourage you. I've only been using vim for about six months and I do not know all the commands and modal changes on this diagram. The great thing about vim is you do not need to know very much to be productive, but every day you learn something new that will make you more productive. While this is a great reference writing a vim plugin or looking up the behaviour of a specific command, I d…
I agree, it's not really a learning tool (for a novice). Some commands here are pretty obscure; you wouldn't use some of them very much or at all, but that's not evident in the diagram. And you also have the right idea about learning vim incrementally ( http://yehudakatz.com/2010/07/29/everyone-who-tried-to-convi... ), instead of the "learn everything in parallel" approach that some advise.
VIM Modes Transition Diagram
11–20 of 37 posts
Re: VIM Modes Transition Diagram
#12As someone who is thinking about learning Vim, this diagram is severely daunting.
I was just watching Bret Victor's Inventing on Principle talk and thus learned about Larry Tesler. He says Larry Tesler dedicated his life to removing modes from software back where was no such thing as modeless editing. Perhaps this is why.
Re: VIM Modes Transition Diagram
#13Earlier quoted context omitted.
I was just watching Bret Victor's Inventing on Principle talk and thus learned about Larry Tesler. He says Larry Tesler dedicated his life to removing modes from software back where was no such thing as modeless editing. Perhaps this is why.
I watched the talk and was caught off guard by his mention of Larry Tesler. I can understand why because that did usher an era of easier to use text editors. However, I'd like to emphasize that there is always a place for tools that are sufficiently complex such that it allows the craftsman wield it proficiently. Past a certain point of simplification, a tool would lack the necessary vocabulary to express things succ…
Re: VIM Modes Transition Diagram
#14In short, this is a woefully incomplete diagram of a summary of a subset of the VIM Mode Transitions. Maybe it could be a start for a serious effort down the line.
I've been using Vim as my main editor for over a dozen years. Nevertheless I'm sure there's mountains of stuff I've never learned or understood that is also left out here, but I'm such a rank beginner that I just don't know to mention it.
Re: VIM Modes Transition Diagram
#15This diagram doesn't include any of the q-macro system, hardly any of the :commands, and only a very vague box saying "operator" for a large class of actions and motions Vim users are constantly engaging in. In short, this is a woefully incomplete diagram of a summary of a subset of the VIM Mode Transitions. Maybe it could be a start for a serious effort down the line. I've been using Vim as my main editor for over a…
Re: VIM Modes Transition Diagram
#16Earlier quoted context omitted.
I watched the talk and was caught off guard by his mention of Larry Tesler. I can understand why because that did usher an era of easier to use text editors. However, I'd like to emphasize that there is always a place for tools that are sufficiently complex such that it allows the craftsman wield it proficiently. Past a certain point of simplification, a tool would lack the necessary vocabulary to express things succ…
I find it interesting that emacs is basically the modeless Vim. I imagine that there are modes involved, but chorded input is basically modeless. I wonder if it makes a difference to the craftsman. Perhaps I should learn emacs to understand the difference.
(commenting from my phone so please excuse weird autocorrect thingies)
Re: VIM Modes Transition Diagram
#17As someone who is thinking about learning Vim, this diagram is severely daunting.