At first this was a bit funny, like playing “Bash Roulette”
…but now it’s getting old lol
Any command in my terminal that exits with non-zero code closes my terminal window
I was told that perhaps I have set -e set in some bash script somewhere that my terminal sources.
I have checked .bash_profile / .bashrc / .profile and it doesn’t look like set -e is in there.
Would there be any other obvious culprits?
Answers:
Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.
Method 1
Alright, so indeed, it was a wayward set -e that caused my trouble.
The way I found the set -e was using bash -lx
The best thing to do would be to use:
bash -lx > lx.log 2>&1
then open that log file and do a search for set…
once you find that wayward set -e you can remove that line and your problem should be gone! (Machine restart might be a good idea tho).
In my case, the set -e was in a file that .bash_profile sources, but the line was not in .bash_profile itself.
Method 2
If you just want to solve the problem, include set +e in your .bashrc — at the end.
You can go digging—there are a lot of other places where a set -e might be—but that will take care of the lot.
If, however, the set -e is part of your $PROMPT_COMMAND then the above will not work. Try printf '%sn' "$PROMPT_COMMAND" and see what’s in it.
All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0