On Fri, 2010-10-22 at 00:55 -0400, William L. Thomson Jr. wrote: > > Speaking of Bash from a developers perspective, I was not aware of the > HISTIGNORE and HISTCONTROL features of bash, till Rob's presentation. :)
Turns out the HISTIGNORE is not so ideal. It also prevents the command from being in any history, which means you can't use the up arrow for the previous command :( Not sure if any other bash tricks to re-invoke the previous command would work. > Going one step further, Kyle mentioned a hack/trick to not write your > current Bash history to the ~/.bash_history file. Kill the shell instead > of exiting it normally. In the spirit of that, a easy way to do that is > the following > > kill -9 $BASHPID In light of the above, and using something Rob also mentioned in his presentation, the alias feature of Bash. I went ahead and added the following alias to my ~/.bash_profile alias bye="kill -9 $BASHPID" That way instead of typing exit, I can just type bye, and it will kill my bash session and nuke any history :) Also another topic Rob covered was Bash completion. Did you know what works for Bash variables as well as other things? Try it out, just type the dollar sign at a terminal and hit tab. $<Tab> Of course that requires bash completion, which might be an add on package to Bash. Check around in your distro's packages for other bash packages. -- William L. Thomson Jr. Obsidian-Studios, Inc. http://www.obsidian-studios.com This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. --------------------------------------------------------------------- Archive http://marc.info/?l=jaxlug-list&r=1&w=2 RSS Feed http://www.mail-archive.com/[email protected]/maillist.xml Unsubscribe [email protected]
