Vim "show my last command" command?

Question

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?

Concertgoer

The best thing I can come up with is this: :echo v:count . v:operator – Joesphjoete

Answer 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.

Knoxville

This didn't work for me for some reason. Turned out history was set to 0. The solution was to run :set history=100 and then I was able to us the up arrow to view previous commands. – Aloysia

I've been trying for years to figure out how to get OUT of this mode. Esc doesn't work. It seems : sometimes works, but not always. I always get stuck in this mode. – Eulogy

while (:) and up/down arrows show command history, (/) up/down arrows show search patterns history. I found that very useful. – Planarian

@devios1: Did you solve it now? It must work, what's the details of your problem? – Precise

Answer 2

q: will show you command history in Vim.
q/ will show you history of searches.
And must importantly, :q will quit the mode.

Reviel

So that's why this feature randomly pops up from time to time. (It's the reverse of :q). I wouldn't have known it existed to go looking for it otherwise. – Impatience

I always get stuck in this mode. How do you get out of it? Esc doesn't work and that really trips me up. – Eulogy

@Eulogy :q will get you out of that mode. I know, very unintuitive and not something we're ever likely to try, because we're so used to :q qutting the editor itself, and it's not obvious that this mode is actually a separate window/split in vim which will intercept the next :q. – Gas

Answer 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.

Quotation

That register stores the last inserted text (after I, A, i, a, s, S, c, C) – Beefcake

Answer 4

Entering colon : then ctrl+p shows your previous command, i.e., moving backward through your vim command history. ctrl+n moves forward.

This is very convenient if you're used to using the command line and prefer not to change your keyboard hand positioning to use arrow keys.

Guddle

Answer 5

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.

Beefcake