3 ms·
I always get trapped in record mode but I don't see that in this diagram. Am I missing something?
by cosmotic 5y ago
I always get trapped in record mode but I don't see that in this diagram. Am I missing something?
- acomar 5y agoq another character begins recording a macro. press q again to finish recording.
- CGamesPlay 5y agoWell, it's not a mode. It's recording, but you can freely change between modes while recording and this will be part of the recording. I believe you can even start a recording in one mode and exit it in another, although this has limited use.
- cosmotic 5y agoIt is most certainly a mode, from a usability standpoint. :q no longer works once in record mode; which fits the definition of modality.
- dvcrn 5y agoq + something else -> starts recording into buffer <something else> q again -> finish recording @ <somethinge else> -> replay recording of buffer <something else>
- alpaca128 5y agoGood summary, but minor addition: `q` is also a valid input. Hitting `qq` starts recording in the `q` buffer, and it stops when the key is pressed a third time in normal mode.
- schemathings 5y agoI recently had the happy discovery that q: puts you into the : buffer, which is your command history. You can navigate to a recent comment and just enter to execute. Bonus point for it being the opposite of :q
- hansvm 5y agoIt's the Q character. That usually happens to me when I mistype a semicolon rather than colon when trying to quit.
- oftenwrong 5y agoQ enters ex mode q is used to start a recording
- hansvm 5y agoThat was imprecision on my part. I should have said "Q key" instead -- the capitalization was to make it stand out.
- cosmotic 5y agoYeah; With basically everything using q to quit, the inconsistency is infuriating. It would be bad enough if it did nothing, but instead of changes modes that you need to explicitly escape before the real quit works.
- mjbrownie 5y agoThe best way to stop doing it accidentally is to start doing it deliberately, then the muscle memory will catch up.