4 ms·
> They're perfectly happy with the speed at which they can edit text and that's fine. I think they miss the point. Speed editing with vim is not about how many
by oelmekki 14y ago
> They're perfectly happy with the speed at which they can edit text and that's fine.
I think they miss the point. Speed editing with vim is not about how many lines you may produce in the day.
It's about the lag between the moment you think about what you want to write and the moment when it's written. Your editor should not be in the way, and that's what vim, when mastered, is all about : you simply don't think about it anymore.
It's for the same reason that vim tries to reduce hand movements, so you won't feel your editor in those extra displacements.
- tyrmored 14y agoYes, I think you've nailed it. See my own reply to this comment.
- minikomi 14y agoAlso, it's extremely satisfying to record a complex macro and then 100@@ it across a wide swath of your file
- mcantor 14y agoRecording macros correctly and quickly is an art. Text objects help immensely, since they can handle a lot of edge cases in different places across your code.
- dasil003 14y agoOne of my favorite tricks was binding @q to <space>. It really speeds up playback so I don't need to necessarily count occurrences or go recursive.
- deleted 14y ago[deleted]
- mistercow 14y ago> It's about the lag between the moment you think about what you want to write and the moment when it's written. I think this is it exactly. In particular, when people start trying to incorporate typing speed into their arguments, it's a sign that they really don't understand where the bottlenecks are.
- snprbob86 14y ago> It's about the lag between the moment you think about what you want to write and the moment when it's written. Agree 100%. Every other editor just feels like swimming in molasses to me.