▲ 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
[–] zemja@programming.dev 12 points 2 years ago (2 children) Can somebody please tell me what history -c is? permalink fedilink source hideshow 4 child comments replies: [–] survivalmachine@beehaw.org 9 points 2 years ago (3 children) history displays a list of all commands you have run on the terminal since the history list was last cleared. It is invaluable for referring back to a big complex command or set of commands you ran at some point in the past. The -c flag clears that history. permalink fedilink source parent hideshow 6 child comments replies: [–] zemja@programming.dev 11 points 2 years ago Fuck, I just cleared my history. permalink fedilink source parent [–] caseyweederman@lemmy.ca 5 points 2 years ago (1 child) What does it do again? permalink fedilink source parent hideshow 2 child comments replies: [–] survivalmachine@beehaw.org 3 points 2 years ago 🤣 permalink fedilink source parent [+] 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 [–] akdas@lemmy.world 6 points 2 years ago* (last edited 2 years ago) It lets you clear the bash command history, either completely or selectively. Here's the GNU docs for the history builtin: https://www.gnu.org/software/bash/manual/html_node/Bash-History-Builtins.html#index-history (I'm not too familiar, someone else can clarify: is this available outside bash?) What's interesting to me is the -a option, which lets you "flush" the history for the current session without ending the session. I can see that being useful! permalink fedilink source parent
[–] survivalmachine@beehaw.org 9 points 2 years ago (3 children) history displays a list of all commands you have run on the terminal since the history list was last cleared. It is invaluable for referring back to a big complex command or set of commands you ran at some point in the past. The -c flag clears that history. permalink fedilink source parent hideshow 6 child comments replies: [–] zemja@programming.dev 11 points 2 years ago Fuck, I just cleared my history. permalink fedilink source parent [–] caseyweederman@lemmy.ca 5 points 2 years ago (1 child) What does it do again? permalink fedilink source parent hideshow 2 child comments replies: [–] survivalmachine@beehaw.org 3 points 2 years ago 🤣 permalink fedilink source parent [+] 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
[–] zemja@programming.dev 11 points 2 years ago Fuck, I just cleared my history. permalink fedilink source parent
[–] caseyweederman@lemmy.ca 5 points 2 years ago (1 child) What does it do again? permalink fedilink source parent hideshow 2 child comments replies: [–] survivalmachine@beehaw.org 3 points 2 years ago 🤣 permalink fedilink source parent
[+] 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
[–] akdas@lemmy.world 6 points 2 years ago* (last edited 2 years ago) It lets you clear the bash command history, either completely or selectively. Here's the GNU docs for the history builtin: https://www.gnu.org/software/bash/manual/html_node/Bash-History-Builtins.html#index-history (I'm not too familiar, someone else can clarify: is this available outside bash?) What's interesting to me is the -a option, which lets you "flush" the history for the current session without ending the session. I can see that being useful! permalink fedilink source parent