On Tue, 2024-06-04 at 16:26 +, Joe Wulf wrote:
It truly depends on how the default management of bash history is set
up in the virgin environment.
Variables like HISTCONTROL, HISTIGNORE can play a part. The setting
for 'shopt -s histappend' also matters.
The BASH man page briefly explains them
If you have 2 separate sessions open for the given user last save/exit
wins and overwrites the history file. This may be an
oversimplification but 2 sessions both saving out do seem to make a
mess.
And if there is no -TERM and/or clean exit then nothing gets written out.
I have trained people on
It truly depends on how the default management of bash history is set up in
the virgin environment.Variables like HISTCONTROL, HISTIGNORE can play a part.
The setting for 'shopt -s histappend' also matters.The BASH man page briefly
explains them.
R,-Joe
On Tuesday, June 4, 2024 at 12:17:4
This is on fedora 40, a fresh 'everything' network install.
I always update/upgrade manually using 'sudo dnf --refresh upgrade'.
To save typing I would scroll through the command history using the
arrow keys.
But 'sudo dnf --refresh upgrade' is no longer listed!
All other commands I used are still
