https://aznot.com/index.php?action=history&feed=atom&title=Linux%2FBash_HistoryLinux/Bash History - Revision history2026-05-07T04:25:55ZRevision history for this page on the wikiMediaWiki 1.41.0https://aznot.com/index.php?title=Linux/Bash_History&diff=5112&oldid=prevKenneth: /* Bash History */2019-03-12T04:43:43Z<p><span dir="auto"><span class="autocomment">Bash History</span></span></p>
<p><b>New page</b></p><div>== Bash History ==<br />
<br />
* Ctrl + R = Incremental search of command history<br />
* Press Ctrl + R again to cycle through history<br />
<br />
<br />
No logging commands to bash history:<br />
<br />
<pre><br />
-------- Original Message --------<br />
Subject: Re: [sllug-members]: Non-root users and BASH shell history<br />
Date: Mon, 20 Apr 2009 10:51:08 -0600<br />
From: Erik Falor <ewfalor@gmail.com><br />
To: Salt Lake Linux Users Group Discussions <sllug-members@sllug.org><br />
<br />
Add the value 'ignorespace' to your $HISTCONTROL variable. It causes<br />
bash to not log commandlines which begin with a space. Then, it's<br />
just a matter of getting into the habit of hitting the spacebar before<br />
entering sensitive commands.<br />
<br />
-- Erik Falor<br />
</pre><br />
<br />
== Do not store history ==<br />
<br />
HISTFILE=<br />
<br />
The most likely cause for history items not to show up is not by setting HISTFILE to nothing or HISTSIZE to zero, it is by logging into the same machine twice and exiting with the second bash instance (in which you did little or nothing) after the one where you did a lot. By default Bash doesn't merge histories and the second Bash-exit overwrites the .bash_history that was so nicely update by the first Bash-exit.</div>Kenneth