Closed davclark closed 9 years ago
bash is usually configured to save history in one file which gets written when the last bash instance exits. At the SCF we save history into tty-specific files so they all get preserved. I can put that bit of bash config into BCE.
Ryan
On Wed, Apr 15, 2015 at 4:29 PM, Dav Clark notifications@github.com wrote:
Have a currently running process, closed a terminal, history was empty. This is easy to reproduce with something like the following as a running process, and click the 'x' on the terminal window:
while [ 0 -lt 1 ] ; do echo 'o crap'; done
Any ideas?
— Reply to this email directly or view it on GitHub https://github.com/ucberkeley/bce/issues/27.
Rad! On Apr 15, 2015 6:34 PM, "Ryan Lovett" notifications@github.com wrote:
bash is usually configured to save history in one file which gets written when the last bash instance exits. At the SCF we save history into tty-specific files so they all get preserved. I can put that bit of bash config into BCE.
Ryan
On Wed, Apr 15, 2015 at 4:29 PM, Dav Clark notifications@github.com wrote:
Have a currently running process, closed a terminal, history was empty. This is easy to reproduce with something like the following as a running process, and click the 'x' on the terminal window:
while [ 0 -lt 1 ] ; do echo 'o crap'; done
Any ideas?
Reply to this email directly or view it on GitHub https://github.com/ucberkeley/bce/issues/27.
Reply to this email directly or view it on GitHub https://github.com/ucberkeley/bce/issues/27#issuecomment-93610527.
Commit 78f9f17 has bash save to ~/.bash_history.d/$n where $n is the number of the tty that bash is running in. It gets written when bash exits.
Have a currently running process, closed a terminal, history was empty. This is easy to reproduce with something like the following as a running process, and click the 'x' on the terminal window:
while [ 0 -lt 1 ] ; do echo 'o crap'; done
Any ideas?