Bash does not remember programs with non 0 exit status in history
- by Amigable Clark Kant
I enter a command. It fails. I press arrow up, modify something and enter it again ... hold it right there.
It used to work like that. Now it's more like:
I enter a command. It fails. I press arrow up, get the last command which didn't fail, likely "ls" or something useless and I type the whole thing again back by hand.
What happened? It wasn't always like this. But it's quite some time since this behavior changed, I'll give you that. Some years ago, at least. How do I put some sanity back into my bash prompt?