realtyvur.blogg.se

That usually means no enter and no ctrl+c. That means no bash prompt display between looking up the number and using it. When using history expansion by number, you should always look up the number immediately before using it. In step 2 we make sure that the line count of $HISTFILE is exactly $HISTSIZE (this means that $HISTFILESIZE must be the same as $HISTSIZE).Ībout the constraints of the history expansion: In step 4 the history counter is raised by the number of lines in $HISTFILE. In step 3 the history counter is reduced by $HISTSIZE.

Step 4 ensures that the commands from the other sessions gets read in to the current session history.īecause step 4 will raise the history counter, we need to reduce the counter in some way. Step 1 ensures that the command from the current running session gets written to the global history file. This is necessary for the history expansion by number (more about this later). The history() function overrides the builtin history to make sure that the history is synchronised before it is displayed. Note that the line count of $HISTFILE is not necessarily $HISTFILESIZE. this will raise the history counter by the amount of lines in $HISTFILE. Read the contents of $HISTFILE and insert them in to the current running session history. This will reduce the history counter by the amount of $HISTSIZE. Setting the special variable $HISTFILESIZE to some value will cause Bash to truncate $HISTFILE to be no longer than $HISTFILESIZE lines by removing the oldest entries.Ĭlear the history of the running session. This will cause $HISTFILE to grow by one line. HISTSIZE=9000īuiltin history the just entered line to the $HISTFILE (default is.

Using Bash version 4.1.5 under Ubuntu 10.04 LTS (Lucid Lynx). This will enable history sharing between bash sessions in a way that the history counter does not get mixed up and history expansion like !number will work (with some constraints).

Here is my attempt at Bash session history sharing.