Just annotations of little "how to's", so I know I can find how to do something I've already done when I need to do it again, in case I don't remember anymore, which is not unlikely. Hopefully they can be useful to others, but I can't guarantee that it will work, or that it won't even make things worse.
Apparently there's some "race condition" that can wipe-out bash history if you break some kinds of loops
At least that's what apparently happened to me.
On Unix' stack exchange I've found this handy way of recovering it, partly at least, if you happen to have another terminal open, from before the wipe-out:
The person who gave this tip suggested doing it in "every terminal", but I believe it would just overwrite it completely for whatever number of times one did it, with the simple ">." In order to not do that and recover some small differences/"ramifications" at the end of the history of each terminal, I guess one would have to do something like that, for one of them, but tweak a bit for the next ones:
For every open terminal, after doing the first command. If these new commands are really that important. Be sure to have ">>" rather than just ">."
https://unix.stackexchange.com/quest.../451016#451016
On Unix' stack exchange I've found this handy way of recovering it, partly at least, if you happen to have another terminal open, from before the wipe-out:
Code:
history | cut -c 8- > histback_user1.txt
Code:
history | cut -c 8- | tail -n [reasonable number] >> histback_user1.txt
https://unix.stackexchange.com/quest.../451016#451016
Total Comments 0
