Using Bash History More Efficiently
If you've used bash for a while you probably know that the commands you enter are saved in the file ~/.bash_history when you log out. Next time you log in, bash automatically loads these history commands from the saved file and you can then use the up and down arrow keys to browse your command history and find the command you want rather than re-entering it.
However, there are more effective ways to use bash's history: you can use Ctrl+R (Control key held down at the same time as the R key). This will display the following in your shell:
(reverse-i-search)`':
If you know type some substring found in the command you're searching for, for example "ls", bash will search for matching commands. For example, it might show:
(reverse-i-search)`ls': lsof -nP -p 3930
What it actually shows is going to be dependent on the commands you've previously entered.
When you do this, bash looks for the last command that you entered that contains the substring "ls", in my case that was "lsof ...". If the command that bash finds is what you're looking for, just hit Enter to execute it. You can also edit the command to suit your current needs before executing it (use the left and right arrow keys to move through it). If you're looking for a different command, hit Ctrl+R again to find a matching command further back in the command history. You can also continue to type a longer substring to refine the search, since searching is incremental.
Note that the substring you enter is searched for throughout the command, not just at the beginning of the command.
Cheng Renquan, Shenzhen, China
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Sponsored by AMD
If you already use virtualized infrastructure, you are well on your way to leveraging the power of the cloud. Virtualization offers the promise of limitless resources, but how do you manage that scalability when your DevOps team doesn’t scale? In today’s hypercompetitive markets, fast results can make a difference between leading the pack vs. obsolescence. Organizations need more benefits from cloud computing than just raw resources. They need agility, flexibility, convenience, ROI, and control.
Stackato private Platform-as-a-Service technology from ActiveState extends your private cloud infrastructure by creating a private PaaS to provide on-demand availability, flexibility, control, and ultimately, faster time-to-market for your enterprise.
Sponsored by ActiveState
| Non-Linux FOSS: libnotify, OS X Style | Jun 18, 2013 |
| Containers—Not Virtual Machines—Are the Future Cloud | Jun 17, 2013 |
| Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer | Jun 12, 2013 |
| Weechat, Irssi's Little Brother | Jun 11, 2013 |
| One Tail Just Isn't Enough | Jun 07, 2013 |
| Introduction to MapReduce with Hadoop on Linux | Jun 05, 2013 |
- Containers—Not Virtual Machines—Are the Future Cloud
- Non-Linux FOSS: libnotify, OS X Style
- Linux Systems Administrator
- Validate an E-Mail Address with PHP, the Right Way
- Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer
- Senior Perl Developer
- Technical Support Rep
- RSS Feeds
- Introduction to MapReduce with Hadoop on Linux
- UX Designer
- Bought photoshop CS5 for developing a website :(
8 min 12 sec ago - What the author describes
1 hour 34 min ago - Reply to comment | Linux Journal
5 hours 44 min ago - Reply to comment | Linux Journal
6 hours 29 min ago - Didn't read
6 hours 40 min ago - Reply to comment | Linux Journal
6 hours 45 min ago - Poul-Henning Kamp: welcome to
8 hours 55 min ago - This has already been done
8 hours 56 min ago - Reply to comment | Linux Journal
9 hours 41 min ago - Welcome to 1998
10 hours 30 min ago
Featured Jobs
| Linux Systems Administrator | Houston and Austin, Texas | Host Gator |
| Senior Perl Developer | Austin, Texas | Host Gator |
| Technical Support Rep | Houston and Austin, Texas | Host Gator |
| UX Designer | Austin, Texas | Host Gator |
| Web & UI Developer (JavaScript & j Query) | Austin, Texas | Host Gator |
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?



Comments
UNIX/Linux
more . bash_history
hs example caveats
The example find/rm commands are not bullet proof
if file names e.g. contain spaces. find and xargs
as well as the other alternative have ways of dealing
with that, so
"man find"and"man xargs";-)I wasn't suggesting the find/rm examples as models for best practice.
But defining an hs function can be handy, and you can put it
in an appropriate bash initialization file to have it available
automatically if you like.
BTW, this
http://tldp.org/LDP/abs/html/
link leads to a lot of good bash tips.
In bash, the history command
In bash, the
historycommand will listthe whole recorded history to stdout, so you can easily
pipe that to grep and search for an arbitrary pattern.
To make that more handy, you can define a function, e.g.,
hs (for history search, hg already existed for me ;-) thus:
[15:33 ~]$ function hs () { history|grep "$@" ; } # don't leave out spaces
Then, if you remember some complex command, e.g., involving
find and rm, you can do something like
[15:33 ~]$ hs 'find.*rm'
225 find .. -type f -iname '*swp' |xargs rm -iv {} \;
228 for f in $(find .. -type f -iname '*swp'); do rm -iv $f;done
533 hs 'find.*rm'
Hm, that command 228 was safer than 225. I remember using echo to
pre-test the action. Look for that:
[15:34 ~]$ hs 'find.*echo'
227 for f in $(find .. -type f -iname '*swp'); do echo "'$f'";done
534 hs 'find.*echo'
[15:34 ~]$
It pays to pay attention to detail if re-executing with
!nnne.g. the find above was below the parent directory at the time. It
won't be what you want to repeat from another place, most likely.
Your history will obviously yield different matches from mine.
BTW, do not arbitrarily remove .swp files!! They are vim's way
of protecting you from yourself ;-) Don't mess with them unless you
know for sure they are no longer needed! I only used that example
because most other commands in my history are trivial to retype.
In my humble opinion, there's only <C-R> useful.
In my humble opinion, there's only most useful.
Other commands like "!tail" starts with "!" are not useful just because I don't trust them only if I see and confirm the whole command. Commands like "!tail" are harmless that it never will destory something, but do you dare to execute "!rm" ? Do you know what will be removed if you don't remember the whole command?
Commands like "!tail:p" are also not very useful that it needs more key strokes. I use and "tail" to check the last commands contains "tail", it needs less key strokes.
Setup extra key bindings in ~/.bash_profile is really useful, for those want to customize something, I just only use the default Bourne-again shell.
Cheng Renquan, Shenzhen, China
Onw nice tip is to use
Onw nice tip is to use Up/Down arrows for forward/backward history search:
# a better up/down arrow key behaviourbind '"\e[A"':history-search-backward
bind '"\e[B"':history-search-forward
Now start typing a command (say - ssh) and hit Up arrow to search for all ssh commands.
Regarding history search with "!".
On July 8th, 2009 Anonymous
# !tail:p
One could:
$ !tail Alt+^which would complete the !tail command (in cases when you are not sure).
Great stuff
Thanks for the main article and the great comments. That is so cool.
Additional tip
Set up the following bindings in your .bashrc or .bash_profile:
# Setup and to act like vi for command line history searching
bind -m vi-insert \C-f:history-search-forward
bind -m vi-insert \C-b:history-search-backward
This allows for Control-B to search back through your history for lines matching the partial command you have already typed. Example:
$ history |tail -10
201 svn checkout -r 5267 .
202 svn update -r 5267
203 ls
204 cd build/
205 ls
206 doxygen Doxyfile 2>&1 | tee doxygen_R5267.log
207 grep c-b ~/.bash*
208 more ~/.bashrc
209 hist |last -10
210 history |tail -10
$ doxy
$ doxygen Doxyfile 2>&1 | tee doxygen_R5267.log
One limitation, it is for Vi-keybinding types.
save time searching through bash history
Good tip. I guess what I'm about to share is also related to this article and most importantly saves you a bit of time when combing through your bash history. In order to execute a command you used before, you can just enter an exclamation mark "!" before the command and it'll be executed.For instance if I ran the command 'tail -n 100' and I wanted to execute it again, instead of typing the whole command, i can just do:
# !tail
and my previous command will be executed. In some cases, you might just want to see the command but not execute it. Then you can do:
# !tail:p
Hope this is useful to someone.