the asciinema demos are super cool! btw asciinema has an option to record input keystrokes as well as screen output, but i don't know if there's a way to display them in the standard js web player for it
the asciinema demos are super cool! btw asciinema has an option to record input keystrokes as well as screen output, but i don't know if there's a way to display them in the standard js web player for it
Update: I installed it and the selection mode is sticky. The command is "wl l l l l"
this kind of thing might be a good ux tradeoff but I think you'd have to validate it empirically to see how much the extra cognitive load slows user task completion
You may also want to try out <num><action> methods while in normal mode.
# Move forward 5 words
5w
# Move 20 lines up
20k
The latter paired with relative line numbering can be really handy.After using vim for a while now I do most of my navigation and editing by searching/replacing
If the next five words begin with the same prefix (happens to me), searching will be wasteful. Just spamming "w" is easier.
But when there's something really distinctive (often, punctuation) near the position I'm aiming for, I'll definitely use search.
That's one of the reasons I prefer BRE over ERE/PCRE when editing text interactively - I can search for punctuation in code without having to backslash-escape it.
'bre vs. ere' is terminology i wasn't familiar with, though i've often tripped over the differences: https://www.gnu.org/software/sed/manual/html_node/BRE-vs-ERE...
iirc mit teco used control characters for its regexp metacharacters to diminish this particular problem