Last parameter of last command in bash in vi-mode

Question

I have been convinced (over at Stack Overflow) to use my beloved bash in vi mode. So far I got used to it quite well and I like it.

However I really do miss one feature: In emacs-mode, you can enter the last parameter of the previous command by pressing "ESC ." (That is, press escape followed by the .)

Is there a default binding to insert the last parameter in vi-mode? I wasn't able to find one and I really miss this command...

Answer 1

There's no default. The binding for 'yank-last-arg' (as listed by 'bind -p') disappears when you switch to vi mode.

bind '"\e."':yank-last-arg

will give you that same binding back (or pick something else)

Answer 2

Not exactly the same, but in either mode you can type !$, and it will be replaced by the last word of the previous command. Find more such things in the manual.

Answer 3

There's (vi-yank-arg), by default mapped to "_". That should do what you want (in command mode).

Answer 4

here is a good list of special bash parameter . I found this while searching meaning of $@.

Answer 5

Inside your .bashrc, add these:

set -o vi
bind -m vi-command ".":insert-last-argument
bind -m vi-insert "\C-l.":clear-screen
bind -m vi-insert "\C-a.":beginning-of-line
bind -m vi-insert "\C-e.":end-of-line
bind -m vi-insert "\C-w.":backward-kill-word

These will restore the default behaviour of not only ESC-dot - but also Ctrl-A, Ctrl-E, Ctrl-W and Ctrl-L. You can therefore enjoy the normal bash vi-mode and still use the shortcuts you know and love. If you need more actions, just check "man bash" to find the name of the readline action you need (like "clear-screen", "end-of-line", etc).

Answer 6

You can use $_ to refer to the last argument of the previous command.

The disadvantages are:

1. You can't verify before pressing Enter that the thing inserted is the thing you intended to insert.

2. If you use PROMPT_COMMAND or a DEBUG trap (I'm not sure which, exactly, causes the problem; I have both in my .bashrc) to do fancy stuff like put the running command into the xterm title, it will clobber $_.