On 8/3/19 11:05 AM, Tomas Janousek wrote:
> Hello,
>
> today I was wondering why I'm sometimes losing history entries and found out
> that bash (5.0.3(1)-release, on Debian testing) won't save the history file
> on closing the terminal window if it's currently sourcing something. I'm
> attaching a script that uses tmux to simulate the scenario. On my system, only
> "test 1" is printed, not "test 2" as expected. I think this is a bug.
I don't have or use tmux, but I'm going to guess that `kill-window' sends
a SIGHUP to the process group and follows it up with a SIGKILL. The
`source' turns off saving to history -- the `source' gets saved in the
history list, not the commands it runs -- and is still running when the
SIGHUP arrives. The SIGHUP causes the shell to exit without saving the
history because history is turned off when the signal handler runs.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU c...@case.edu http://tiswww.cwru.edu/~chet/
