merged
authorOleksandr Gavenko <gavenkoa@gmail.com>
Tue, 27 Oct 2009 14:49:39 +0200
changeset 222 221500927a59
parent 221 97171c12b447 (diff)
parent 220 10d0d94eabde (current diff)
child 225 0de8b66b6f49
child 236 465209f16b3a
merged
--- a/bash.rst	Fri Oct 16 12:15:04 2009 +0300
+++ b/bash.rst	Tue Oct 27 14:49:39 2009 +0200
@@ -8,9 +8,32 @@
 
   PS1='\u@\H$ '
 
-When xterm start bash - it start as nonlogin. So ~/.bash_profile and ~/.bashrc
+When xterm start bash - it start as non-login. So ~/.bash_profile and ~/.bashrc
 didn't read. To workaround this use
 
   $ xterm -e bash -i -c "mc -x"
 
-That make bash interactive and init file readed.
+That make bash interactive and init file read.
+
+* Command history.
+
+Bash allow accessing to command that you type previously. There are exist
+several options to control command history behavior. Set corresponding
+variables in your ~/.bashrc file (which is read by interactive shell):
+
+  #   ignorespace do not save lines that start with space
+  #   erasedups all previous lines matching the current line to be removed from
+  #             the history list before that line is saved
+  export HISTCONTROL=igrorespace:erasedups
+  export HISTIGNORE=" ?cd *":"e *":"sudo mv *":"sudo rm *":"sudo cp *":"sudo mkdir *":"sudo chmod *":"sudo chown *":ls:pwd:"vlc*"
+
+There are another options, with default values (which satisfy my neediness, so
+I don't put they to ~/.bashrc):
+
+  export HISTFILE=~/.bash_history  # where is command history stored
+  export HISTFILESIZE=500          # how many lines been in $HISTFILE
+  export HISTSIZE=500              # how many lines been stored in bash process
+
+** mc (GNU Midnight Commander).
+
+You can also set special history rules for mc subshell in ~/.mc/bashrc file.