-
-
Notifications
You must be signed in to change notification settings - Fork 101
Open
Description
What Happened?
My Terminal bash history is patchy. I can understand when using multiple tabs, history can get mangled so I've started using a single tab. However, just after reboot I can't find the most recent command I ran and have to Google it again.
Steps to Reproduce
Steps to reproduce:
- Open Terminal
- type command
foo - close Terminal
- Open Terminal
- type command
bar - sudo reboot
- log in after reboot
- Open Terminal
history
Expected results:
output includes "foo" and then "bar"
Actual results:
output "foo"
Expected Behavior
When Terminal catches signal from system reboot, it should allow bash shell to save the session history.
Terminal should be trapping all necessary signals, including whichever signal is sent from sudo reboot
OS Version
7.x (Horus)
Software Version
Latest release (I have run all updates)
Log Output
N/A (I tried pasting the output from `dmesg` but it was too long for the form. I'm happy to provide further info on request)Hardware Info
MacbookPro7,1, 16GB RAM
bcmwl-kernel-sources driver is installed
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels