On Thu, 2010-10-21 at 08:45 -0400, Rafael Troncoso wrote: > Rob, > the presentation was pretty good, it was a good refreshing and of > course learned new few things. I am a developer, but as you said, bash > scripting is a different world and every time I need to write > something in bash, I spend more time in Google than actually writing > the script.
Speaking of Bash from a developers perspective, I was not aware of the HISTIGNORE and HISTCONTROL features of bash, till Rob's presentation. :) Which if your running common commands over and over, like compiling and/or testing an app, or simply things like ls, ps, etc. You can add those to HISTIGNORE. Also you can set HISTCONTROL to not store duplicate entries, and/or spaces. http://www.gnu.org/software/bash/manual/html_node/Bash-Variables.html#index-HISTCMD-197 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 -- William L. Thomson Jr. Obsidian-Studios, Inc. http://www.obsidian-studios.com --------------------------------------------------------------------- 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]
