3 ms·

You mean “esc, d, d, ., ., ., ., esc” which is two mode changes, eight key strokes of three different types. Versus five identical key strokes with VSCode. Next

You mean “esc, d, d, ., ., ., ., esc” which is two mode changes, eight key strokes of three different types. Versus five identical key strokes with VSCode. Next. Also define “smooth flow”. I my experience pair programming, by the time you are starting you command after choosing among all possibilities, I have already performed the change with VSCode.

colordrops 5y ago
No. First, you don't hit esc at the end to get back into insert mode, assuming that's what you mean - you'd hit "i". Also, it doesn't make sense to include mode changes since you don't know what mode you are in to begin with or what mode you want to be in when you are done. Lastly, this is all you need: 5dd But as long as you are including preparation keystrokes, how may keystrokes would it be to get to a particular line in vscode? I guarantee it will be a lot more than vim. There are countless ways to navigate to a position in a buffer.
- crubier 5y ago
  I cmd-arrow + click on it on my MacBook trackpad if needed. Believe it or not, it’s actually really really fast, and in my experience faster than any vim trick. The reason why it’s faster is that it’s a lower level task: I can just visually go where I want without even having to read contents or even line numbers, just based on text shape, don’t even have to think about it, it’s just muscle reflex. I don’t have to (consciously or not) plan a strategy choosing the best way among 5 different ways each time I want to select text. And no, this never becomes a true reflex. If it does then it’s just because you always choose the same strategy. You always have this part of your brain that has to think about vim tricks, and believe me, we can see that from the outside.
opan 5y ago
If you really use vim, you typically are "always" in normal mode. When you want to type text, you go into insert mode, and you leave it when you're done. If you sit around in insert mode, you miss out on a lot of utility. >Also define “smooth flow”. I my experience pair programming, by the time you are starting you command after choosing among all possibilities, I have already performed the change with VSCode. There's really not much thought involved. If you can imagine yourself using keyboard shortcuts, it's probably pretty similar. In a simple example, you don't think "I gotta hold ctrl, press c, release c, and then release ctrl", you just think "I'm going to copy this". I think you have the idea that vim is really complicated and its users must be bogged down and thinking more. At worst I would say it's probably the same as what you have now, unless you count very early stages where you actually just don't know your way around too well. When you're situated and experienced, it's not ever slower in my experience. On the contrary I feel a bit disabled when I have to edit in something without vim keys. It's not like I can't jump around with home/end and select text with ctrl-shift-arrows and whatnot, but it doesn't feel as fast or comfortable or natural to me.

colordrops 5y ago

No. First, you don't hit esc at the end to get back into insert mode, assuming that's what you mean - you'd hit "i". Also, it doesn't make sense to include mode changes since you don't know what mode you are in to begin with or what mode you want to be in when you are done. Lastly, this is all you need: 5dd But as long as you are including preparation keystrokes, how may keystrokes would it be to get to a particular line in vscode? I guarantee it will be a lot more than vim. There are countless ways to navigate to a position in a buffer.

crubier 5y ago
I cmd-arrow + click on it on my MacBook trackpad if needed. Believe it or not, it’s actually really really fast, and in my experience faster than any vim trick. The reason why it’s faster is that it’s a lower level task: I can just visually go where I want without even having to read contents or even line numbers, just based on text shape, don’t even have to think about it, it’s just muscle reflex. I don’t have to (consciously or not) plan a strategy choosing the best way among 5 different ways each time I want to select text. And no, this never becomes a true reflex. If it does then it’s just because you always choose the same strategy. You always have this part of your brain that has to think about vim tricks, and believe me, we can see that from the outside.

opan 5y ago

If you really use vim, you typically are "always" in normal mode. When you want to type text, you go into insert mode, and you leave it when you're done. If you sit around in insert mode, you miss out on a lot of utility. >Also define “smooth flow”. I my experience pair programming, by the time you are starting you command after choosing among all possibilities, I have already performed the change with VSCode. There's really not much thought involved. If you can imagine yourself using keyboard shortcuts, it's probably pretty similar. In a simple example, you don't think "I gotta hold ctrl, press c, release c, and then release ctrl", you just think "I'm going to copy this". I think you have the idea that vim is really complicated and its users must be bogged down and thinking more. At worst I would say it's probably the same as what you have now, unless you count very early stages where you actually just don't know your way around too well. When you're situated and experienced, it's not ever slower in my experience. On the contrary I feel a bit disabled when I have to edit in something without vim keys. It's not like I can't jump around with home/end and select text with ctrl-shift-arrows and whatnot, but it doesn't feel as fast or comfortable or natural to me.