Vim “show my last command” command?

问题:

Is there a command which shows what was the last command in normal mode?

Suppose I accidently hit random key and got some unexpected result. Sure I can undo it, but could I reveal what key was pressed and how it was interpreted?

回答1:

Hit the colon (:) and then use the up arrow to start going back through previous commands. You can use the up/down arrows too to move around the list.

回答2:

q: will show you command history in Vim. q/ will show you history of searches

回答3:

The text from the last command is stored in the . register. You can see all registers by :display. Unfortunately it doesn't say what the started the normal command.

To see commands from : (command mode) you can use :hist or q: which is limited to the last 20 (by default).

Another ability is to save the undo buffer :wundo undo.bin -- but the undo buffer is binary.

But none of these actually answer your question. I'm curious if it can be done.

回答4:

It is difficult to know it. You can play with the variables:

v:operator
v:count (and v:prevcount)
v:register

But you cannot fully get the last normal mode command issued.

However if you want to systematically record everything you type while in Vim, you can launch vim -W ~/.vim-last-scriptout (a Windows version: vim -W "%HOMEPATH%\Vim\.last-scriptout) You can alias it in your shell on a UNIX machine. Every single key, or control-key, will be recorded into that file. Note that if you happen to use gvim or vim -g (the GUI) you might encounter this bug.

If you want to replay this file you can use :source! (with the exclamation mark) or the -s option from the command line.

On Windows I have set gvimportable.exe -W gvim_directory\last_scriptout as my default editor in my Commander program (FreeCommander). This way I can always remember what I have typed to do something and repeat a sequence of commands on another file. Of course I have another shortcut for opening Vim and playing the scriptout.

Note that the file might be written only when Vim exits, so you have to lose your session to know what you've done.