mirror of
https://github.com/dcarrillo/prezto.git
synced 2025-10-24 10:29:08 +00:00
Zsh and Prezto files don't always reside in `~/`. Instead, they have
a more spec compliant location (`${ZDOTDIR:-$HOME}/`). Make them
unambiguous in the documentation. Likewise, for `$GNUPGHOME`.
Further, add instruction for optionally setting up Prezto in
`$XDG_CONFIG_HOME`.
While at this, also add clarification on relative ordering of some of
the modules, apply more formatting tweaks and doc improvements.
History
Sets history options and defines history aliases.
Note: Default path of HISTFILE has changed from
${ZDOTDIR:-$HOME}/.zhistory to ${ZDOTDIR:-$HOME}/.zsh_history. The file
will be automatically renamed if possible (when the new one doesn't exist).
Otherwise, if you want to preserve previous history, you will need to move them
from ${ZDOTDIR:-$HOME}/.zhistory to ${ZDOTDIR:-$HOME}/.zsh_history.
Alternately, you can set HISTFILE manually to ${ZDOTDIR:-$HOME}/.zhistory.
Options
BANG_HISTtreats the ! character specially during expansion.EXTENDED_HISTORYwrites the history file in the :start:elapsed;command format.SHARE_HISTORYshares history between all sessions. Note thatSHARE_HISTORY,INC_APPEND_HISTORY, andINC_APPEND_HISTORY_TIMEare mutually exclusive.HIST_EXPIRE_DUPS_FIRSTexpires a duplicate event first when trimming history.HIST_IGNORE_DUPSdoes not record an event that was just recorded again.HIST_IGNORE_ALL_DUPSdeletes an old recorded event if a new event is a duplicate.HIST_FIND_NO_DUPSdoes not display a previously found event.HIST_IGNORE_SPACEdoes not record an event starting with a space.HIST_SAVE_NO_DUPSdoes not write a duplicate event to the history file.HIST_VERIFYdoes not execute immediately upon history expansion.HIST_BEEPbeeps when accessing non-existent history.
Variables
HISTFILEstores the path to the history file.HISTSIZEstores the maximum number of events to save in the internal history.SAVEHISTstores the maximum number of events to save in the history file.
Aliases
history-statlists the ten most used commands
Authors
The authors of this module should be contacted via the issue tracker.