VIM Modes Transition Diagram
stevelosh.com
VIM Modes Transition Diagram
1–10 of 37 posts
Re: VIM Modes Transition Diagram
#2As someone who is thinking about learning Vim, this diagram is severely daunting.
Re: VIM Modes Transition Diagram
#3As someone who is thinking about learning Vim, this diagram is severely daunting.
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 don't really see it as a learning tool.
Re: VIM Modes Transition Diagram
#4As 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
#5As someone who is thinking about learning Vim, this diagram is severely daunting.
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.
Re: VIM Modes Transition Diagram
#6As someone who is thinking about learning Vim, this diagram is severely daunting.
Speaking as somebody who learned Vim two years ago, I'm able to follow this diagram and recognize most of it, but in everyday flight I don't use all of it.
A little bit every day and you'll be there in no time.
EDIT: I should say, I took some time to go through every part of the diagram and it's been very helpful for forming a better mental model of Vim. It will look scary to the beginner, but for the moderate to advanced vimmer, this is a very useful learning tool provided you take some time to understand.
The thing about diagrams is that they often encode as much information as you might find in an essay, yet since the information is presented all at once, we have the expectation that we should be able to understand it immediately. It should take 10-20 minutes to understand this diagram.
Re: VIM Modes Transition Diagram
#7As someone who is thinking about learning Vim, this diagram is severely daunting.
I am pretty proficient in Vim and this diagram scares me. I can understand it if I try, but it does nothing to improve my intuitive sense of Vim commands.
Don't let this scare you. Learn 10 basic Vim principles and they will serve you 95% of the time. All this extra stuff can be learned incrementally on a case-by-case basis.
Re: VIM Modes Transition Diagram
#8As someone who is thinking about learning Vim, this diagram is severely daunting.
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…
Au contraire, I find this to be a great learning tool. As a post-novice vimmer, this is the first time that I've been able to see it all laid out like this so that I can see what I know already, what's left to learn and how it all fits together. I didn't even know "select mode" existed before this (though I promise I'll never use it – even MacVim uses visual mode with the mouse). I've saved this to my help/vim folder and I plan to refer to it periodically.
Re: VIM Modes Transition Diagram
#9As someone who is thinking about learning Vim, this diagram is severely daunting.
I've been using Vim exclusively for about 2 years now, and I don't even want to begin to know what the hell is going on in that diagram. It was clearly not created for the purpose of teaching Vim but probably as an exercise of mapping out all the possible transitions between various modes and motions. Cool beans, but I hope the novices don't mistake it for something else.
If you're still on the edge about Vim, there have been a few good articles on how to begin learning it. What worked for me personally was learning the very basics, how to enter insert mode, how to save and quit, and starting to use Vim as a regular mode-less editor while slowly learning about various useful things you can do in normal mode ("hey, I can delete a word or a line with two key presses"). That way you can begin to extract use out of it immediately while growing increasingly efficient with other modes.
If you're on a Mac, MacVim gives you native OS X shortcuts for things like Copy/Paste, and maps selecting text with the mouse to visual mode which, combined with using insert mode, gives you the same functionality as a regular mode less editor would.
Re: VIM Modes Transition Diagram
#10As 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.
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 succinctly. Like why Jargon is necessary sometimes.
However, I think Vim is fundamentally a finite state machine. While complex, once you grok the mental model of how it works, everything else comes quite naturally. So fear not.