diff options
author | Wayne Davison <wayned@users.sourceforge.net> | 2005-03-18 22:40:17 +0000 |
---|---|---|
committer | Wayne Davison <wayned@users.sourceforge.net> | 2005-03-18 22:40:17 +0000 |
commit | 70c4511893bed1c303cff4f646b0f3b69184b04f (patch) | |
tree | 5b608adadd1662ff9c0e847af398bac00e100790 | |
parent | 63f6742e9aae5238c83c3c7223a29e044e45d66f (diff) | |
download | zsh-70c4511893bed1c303cff4f646b0f3b69184b04f.tar.gz zsh-70c4511893bed1c303cff4f646b0f3b69184b04f.tar.xz zsh-70c4511893bed1c303cff4f646b0f3b69184b04f.zip |
Document the HIST_SAVE_BY_COPY option and made a few tweaks to
the history-appending options.
-rw-r--r-- | Doc/Zsh/options.yo | 28 |
1 files changed, 22 insertions, 6 deletions
diff --git a/Doc/Zsh/options.yo b/Doc/Zsh/options.yo index a49253e72..fd21265ed 100644 --- a/Doc/Zsh/options.yo +++ b/Doc/Zsh/options.yo @@ -468,9 +468,12 @@ pindex(APPEND_HISTORY) cindex(history, appending to a file) item(tt(APPEND_HISTORY) <D>)( If this is set, zsh sessions will append their history list to -the history file, rather than overwrite it. Thus, multiple parallel -zsh sessions will all have their history lists added to the -history file, in the order they are killed. +the history file, rather than replace it. Thus, multiple parallel +zsh sessions will all have the new entries from their history lists +added to the history file, in the order that they exit. +The file will still be periodically re-written to trim it when the +number of lines grows 20% beyond the value specified by +tt($SAVEHIST) (see also the HIST_SAVE_BY_COPY option). ) pindex(BANG_HIST) cindex(history, enable substitution) @@ -562,6 +565,18 @@ item(tt(HIST_REDUCE_BLANKS))( Remove superfluous blanks from each command line being added to the history list. ) +pindex(HIST_SAVE_BY_COPY) +item(tt(HIST_SAVE_BY_COPY))( +When the history file is re-written, we normally write out a copy of +the file named $HISTFILE.new and then rename it over the old one. +However, if this option is unset, we instead truncate the old +history file and write out the new version in-place. If one of the +history-appending options is enabled, this option only has an affect +when the enlarged history file needs to be re-written to trim it +down to size. Disable this only if you have special needs, as this +makes it possible to lose history entries if zsh gets interrupted +during the save. +) pindex(HIST_SAVE_NO_DUPS) item(tt(HIST_SAVE_NO_DUPS))( When writing out the history file, older commands that duplicate @@ -579,9 +594,10 @@ cindex(history, incremental appending to a file) item(tt(INC_APPEND_HISTORY))( This options works like tt(APPEND_HISTORY) except that new history lines are added to the tt($HISTFILE) incrementally (as soon as they are -entered), rather than waiting until the shell is killed. -The file is periodically trimmed to the number of lines specified by -tt($SAVEHIST), but can exceed this value between trimmings. +entered), rather than waiting until the shell exits. +The file will still be periodically re-written to trim it when the +number of lines grows 20% beyond the value specified by +tt($SAVEHIST) (see also the HIST_SAVE_BY_COPY option). ) pindex(SHARE_HISTORY) cindex(share history) |