Reputation: 11820
Just a question to improve my bash
skills. I always do this:
$ history | grep some_long_command
...
...
123 some_long_command1.........
124 some_long_command2.........
...
I can then run the command the command I found by doing:
!123
However, I often want to do this:
some_long_command1foobar
I.e. change the command before I run it. Can you use bash to run this command instead:
#some_long_command1
so it gets commented.
Then I don't have to use my mouse to highlight the command, edit it and then run it (I can just use the keyboard - faster).
I suppose I could write a script to do it but there might already be functionality built in somewhere....?
Upvotes: 81
Views: 53407
Reputation: 1
Put
alias r='fc -s'
in your .bashrc
(home dir)
then you can just type in
r <whatever>
at the command prompt and you will execute a copy of the last <whatever>
command (same params) that is in your history. just hit up arrow to see what you have executed if you feel the need.
Upvotes: 0
Reputation: 812
You may wan to try "suggest box"-like history https://github.com/dvorka/hstr - it reads Bash history and allows for quick navigation.
To get the last command simply type hh, navigate to the command and use right arrow to get it on command line (where you can edit it and/or add comment).
Upvotes: 1
Reputation: 1962
Actually, you can just append :p
to the command to print it without actually running it. For example:
$ ls -la
$ !!:p
Will print out ls -la
as the previous command without running it, and you can just press ↑ (up) to find it and edit it.
You can also do
!123:p
to print out the 123rd command as your previous command.
Upvotes: 63
Reputation: 15675
I'd suggest instead of using the history command, you use ctrl+r
and start typing that command. When you press an arrow key as if to go to modify it, it will drop out of autocomplete recognition, and will let you edit before running.
UPDATE: also, if you want to cycle through the different commands that contain the string you just typed, keep on pressing ctrl+r
Upvotes: 147
Reputation: 28160
Instead of using the history
command, bind history-search-backward
/history-search-forward
to key shortcuts which can be remembered easily (I prefer PgUp/PgDown). To do that, put this into your .inputrc
file:
"<key code>": history-search-backward
"<key code>": history-search-forward
To get <key code>
, type Ctrl-V <key>
in the shell, and replace the starting ^[
with \e
in whatever was output.
After this is set up, you can just type some
and press PgUp to get some_long_command
. If you need some_long_command with_some_arg
but there is a similar command some_long_command with_some_other_arg
later in the history, you can cycle through until you reach it by typing some
and then hitting PgUp repeatedly, or you can type some
, hit PgUp, move the cursor to where the two commands start to differ, type a few characters and hit PgUp once more. This ability to quickly page through / differentiate between similar commands makes it in my opinion a much more comfortable tool than Ctrl-R
.
Upvotes: 4
Reputation: 9026
You can get to edit mode by hitting M-^ (option-shift-6 on a mac).
Type this:
!123M-^
And you'll be editing command #123. It's sort of like using ctrl-r, but starting with exclamation-point syntax.
Upvotes: 6
Reputation: 63698
You can also try fc
command to edit the command in the history.
fc is a standard program on Unix that lists or edits and reexecutes, commands previously entered to an interactive shell. fc is a built-in command in the bash shell; help fc will show usage information.
Apart from reverse-incremental search(Ctrl+R), we have some more bash shortcuts:
From man bash
:
previous-history (C-p) Fetch the previous command from the history list, moving back in the list. next-history (C-n) Fetch the next command from the history list, moving forward in the list. beginning-of-history (M-<) Move to the first line in the history. end-of-history (M->) Move to the end of the input history, i.e., the line currently being entered. reverse-search-history (C-r) Search backward starting at the current line and moving 'up' through the history as necessary. This is an incremental search. forward-search-history (C-s) Search forward starting at the current line and moving 'down' through the history as necessary. This is an incremental search. non-incremental-reverse-search-history (M-p) Search backward through the history starting at the current line using a non-incremental search for a string supplied by the user. non-incremental-forward-search-history (M-n) Search forward through the history using a non-incremental search for a string supplied by the user. yank-nth-arg (M-C-y) Insert the first argument to the previous command (usually the second word on the previous line) at point. With an argument n, insert the nth word from the previous command (the words in the previous command begin with word 0). A negative argument inserts the nth word from the end of the previous command. Once the argument n is computed, the argument is extracted as if the "!n" history expansion had been specified. yank-last-arg (M-., M-_) Insert the last argument to the previous command (the last word of the previous history entry). With an argument, behave exactly like yank-nth-arg. Successive calls to yank-last-arg move back through the history list, inserting the last argument of each line in turn. The history expansion facilities are used to extract the last argument, as if the "!$" history expansion had been specified. shell-expand-line (M-C-e) Expand the line as the shell does. This performs alias and history expansion as well as all of the shell word expansions. See HISTORY EXPANSION below for a description of history expansion. history-expand-line (M-^) Perform history expansion on the current line. See HISTORY EXPANSION below for a description of history expansion. insert-last-argument (M-., M-_) A synonym for yank-last-arg. operate-and-get-next (C-o) Accept the current line for execution and fetch the next line relative to the current line from the history for editing. Any argument is ignored. edit-and-execute-command (C-xC-e) Invoke an editor on the current command line, and execute the result as shell commands.
Upvotes: 20
Reputation: 531125
You can also put
shopt -s histverify
in your .bash_profile
, which causes any history expansion to appear on your command line without running it, allowing you to edit before doing so.
Upvotes: 3
Reputation: 2923
!123:gs/old/new/
Will run command 123 replacing the string 'old' with the string 'new'.
Upvotes: 11