Timeline for Any command in my terminal that exits with non-zero code closes my terminal window
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 2, 2023 at 22:26 | answer | added | jewbix.cube | timeline score: 2 | |
| Oct 13, 2023 at 2:30 | comment | added | jewbix.cube | What if set +e does not fix the problem? | |
| Nov 30, 2017 at 22:33 | vote | accept | Alexander Mills | ||
| Nov 28, 2017 at 12:57 | comment | added | David Foerster | You can inspect the set of currently enabled shell flags with the special variable - like so: echo $-. | |
| Nov 28, 2017 at 10:49 | history | tweeted | twitter.com/StackUnix/status/935460633474207744 | ||
| Nov 28, 2017 at 5:28 | answer | added | Alexander Mills | timeline score: 24 | |
| Nov 28, 2017 at 3:23 | comment | added | muru | PS4=' ${BASH_SOURCE}:$LINENO: ' bash -lixc true |& grep -e set -e trap could be informative. | |
| Nov 27, 2017 at 23:21 | answer | added | Wildcard | timeline score: 14 | |
| Nov 27, 2017 at 23:21 | comment | added | egmont | Execute a set +e, does it repair the problem? If so, which I assume, then you need to keep looking for that set -e. It could be in the global versions of these files under /etc, or in any other script sourced from them. Move your config files away, if the problem is fixed then add back the lines in smaller chunks to see where it breaks. | |
| Nov 27, 2017 at 23:13 | history | asked | Alexander Mills | CC BY-SA 3.0 |