▲ 136 ▼ WDYM your terminal isn't a test suite? (lemmy.tf) submitted 2 years ago by sabreW4K3@lemmy.tf to c/programmer_humor@programming.dev 31 comments fedilink hide all child comments
[+] umbrella@lemmy.ml 3 points 2 years ago* (last edited 1 year ago) (1 child) [deleted] permalink fedilink source parent hideshow 2 child comments replies: [–] survivalmachine@beehaw.org 1 point 2 years ago* Yes, my comment only applies to the shell history in memory. -c clears history immediately, but you can still reload it from disk if you haven't overwritten that with -w. If you tend to close your terminal windows frequently and rely on the history feature between sessions, it would benefit you to learn about the intricacies of the on-disk copy of history and how its affected by writes, appends, clears, crashes, etc. I tend to leave my terminal windows open a long time and copy any complex commands out to my PKM if I need to save them for future sessions, so I generally try not to rely on .bash_history, but it has saved my bacon on more than one occasion. permalink fedilink source parent
[–] survivalmachine@beehaw.org 1 point 2 years ago* Yes, my comment only applies to the shell history in memory. -c clears history immediately, but you can still reload it from disk if you haven't overwritten that with -w. If you tend to close your terminal windows frequently and rely on the history feature between sessions, it would benefit you to learn about the intricacies of the on-disk copy of history and how its affected by writes, appends, clears, crashes, etc. I tend to leave my terminal windows open a long time and copy any complex commands out to my PKM if I need to save them for future sessions, so I generally try not to rely on .bash_history, but it has saved my bacon on more than one occasion. permalink fedilink source parent