267a721ac6
...and hide errors relating to setting already-readonly variables. `plugin/history-eternal` does not need to force loading after `plugin/history` because both plugins will play nicely with read-only variables, and since we're overwritting and marking read-only then the intended result survives no matter which loads first. plugin/history-eternal: require Bash v4.3+ Unlimited history is only possible in _Bash_ version 4.3 and up
23 lines
952 B
Bash
23 lines
952 B
Bash
# shellcheck shell=bash
|
|
about-plugin 'eternal bash history'
|
|
|
|
if [[ ${BASH_VERSINFO[0]} -lt 4 ]] || [[ ${BASH_VERSINFO[0]} -eq 4 && ${BASH_VERSINFO[1]} -lt 3 ]]; then
|
|
_log_warning "Bash version 4.3 introduced the 'unlimited' history size capability."
|
|
return 1
|
|
fi
|
|
|
|
# Modify history sizes before changing location to avoid unintentionally
|
|
# truncating the history file early.
|
|
|
|
# "Numeric values less than zero result in every command being saved on the history list (there is no limit)"
|
|
readonly HISTSIZE=-1 2> /dev/null || true
|
|
|
|
# "Non-numeric values and numeric values less than zero inhibit truncation"
|
|
readonly HISTFILESIZE='unlimited' 2> /dev/null || true
|
|
|
|
# Use a custom history file location so history is not truncated
|
|
# if the environment ever loses this "eternal" configuration.
|
|
HISTDIR="${XDG_STATE_HOME:-${HOME?}/.local/state}/bash"
|
|
[[ -d ${HISTDIR?} ]] || mkdir -p "${HISTDIR?}"
|
|
readonly HISTFILE="${HISTDIR?}/history" 2> /dev/null || true
|