{"id":76,"date":"2013-07-01T05:02:54","date_gmt":"2013-07-01T05:02:54","guid":{"rendered":"http:\/\/ubuntuhandbook.org\/?p=76"},"modified":"2024-04-01T06:52:46","modified_gmt":"2024-04-01T06:52:46","slug":"how-to-run-the-history-commands-quickly-and-easily","status":"publish","type":"post","link":"https:\/\/ubuntuhandbook.org\/index.php\/2013\/07\/how-to-run-the-history-commands-quickly-and-easily\/","title":{"rendered":"How to Re-Run History Commands Quickly in Ubuntu"},"content":{"rendered":"

\"\"<\/a><\/p>\n

Most Linux remembers the commands that you ran in terminal or command console. It’s useful for finding out what you’ve done to the system, especially for server.<\/p>\n

For frequently used command with a long code, you don’t need to type all the code again and again. You can re-run then using history commands option, by just a few key presses.<\/p>\n

List history commands<\/h3>\n

To find out what commands you’ve run in your Linux, simply run command:<\/p>\n

history<\/pre>\n
In the output, you’ll see a large list of commands that you ran before. And, each command has number at its beginning.
\n\"\"<\/a><\/p>\n
If you have too much history commands, it may be hard to browse and find out a certain command. In the case, add grep<\/code> option to filter. For example, run command below to find out history commands that include apt install<\/code>.<\/p>\n
history | grep \"apt install\"<\/pre>\n
For choice, you may also add -E<\/code> option after grep<\/code> to filter with regular expressions.
\n\"\"<\/a><\/p>\n
Re-Run a History Command<\/h3>\n
Once you got the history command, that’s too long or you don’t remember, you can simply re-run it by typing !number<\/b>, where number is the number in front of that command in history output.<\/p>\n
For example, run command below will re-run sudo apt install gimp<\/code>, according to last screenshot. And, in terminal window it outputs what’s going to run immediately after you hitting Enter. If it’s a sudo<\/code> command, it will also ask for password authentication.<\/p>\n
!1057<\/pre>\n
\"\"<\/a><\/p>\n
To avoid careless mistakes, you may use the command below instead by adding :p<\/code> in end to first preview that history command:<\/p>\n
!1057:p<\/pre>\n
Then re-run !1057<\/code> if you confirm it is indeed the command you want.<\/p>\n
\"\"<\/a><\/p>\n
<\/pre>\n
For the last command, without finding out the history number, just use command below will re-run it:<\/p>\n
!!<\/pre>\n
And, you can use it along with other commands. For example, re-run last command with sudo<\/code> permission:<\/p>\n
sudo !!<\/pre>\n
Or re-run last command, then poweroff:<\/p>\n
!! && poweroff<\/pre>\n
There are also more choices, for example, re-run the last command start with given string:<\/p>\n
!sudo<\/pre>\n
The command will re-run the last command start with sudo<\/code>.<\/i><\/p>\n
And, all the commands above can follow with :p<\/code> to preview command before running.<\/p>\n
\"\"<\/a><\/p>","protected":false},"excerpt":{"rendered":"
Most Linux remembers the commands that you ran in terminal or command console. It’s useful for finding out what you’ve done to the system, especially for server. For frequently used command with a long code, you don’t need to type all the code again and again. You can re-run then using history commands option, by […]<\/p>\n","protected":false},"author":1,"featured_media":37909,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11],"tags":[19],"class_list":["post-76","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-command-skills","tag-command-skill"],"_links":{"self":[{"href":"https:\/\/ubuntuhandbook.org\/index.php\/wp-json\/wp\/v2\/posts\/76","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ubuntuhandbook.org\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ubuntuhandbook.org\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ubuntuhandbook.org\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ubuntuhandbook.org\/index.php\/wp-json\/wp\/v2\/comments?post=76"}],"version-history":[{"count":0,"href":"https:\/\/ubuntuhandbook.org\/index.php\/wp-json\/wp\/v2\/posts\/76\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ubuntuhandbook.org\/index.php\/wp-json\/wp\/v2\/media\/37909"}],"wp:attachment":[{"href":"https:\/\/ubuntuhandbook.org\/index.php\/wp-json\/wp\/v2\/media?parent=76"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ubuntuhandbook.org\/index.php\/wp-json\/wp\/v2\/categories?post=76"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ubuntuhandbook.org\/index.php\/wp-json\/wp\/v2\/tags?post=76"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}