Timeline for Recommended way for a Linux app to inform user of an exception
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 27 at 13:34 | comment | added | marcelm | At the very least, always report the error to stderr, and exit with non-0 exit status. You may (or may not) be able to do more, but those two are crucial. | |
| May 27 at 10:38 | answer | added | Simon Richter | timeline score: 0 | |
| May 25 at 18:54 | comment | added | Glenn Willen | The usual answer is "poorly". I think there's already a good variety of options in the answers here, but in general I would say that the bar is low. | |
| May 25 at 7:41 | answer | added | Keiji | timeline score: 11 | |
| May 25 at 1:17 | answer | added | Ángel | timeline score: 15 | |
| May 24 at 23:18 | comment | added | Solomon Slow | FWIW: Linux strives for compatibility with another family of operating systems whose owners pay big $$$ to use a certain name that ends with "nix." Back when the ancient ancestors of those *nix operating systems roamed the Earth, there was no GUI, and there were no "apps," and one of the guiding principles was that pretty much any program could be execd by some other program. Programmers, therefore, were strongly encouraged to encode most of what the "user" (who might actually be another program) needed to know about why a program failed in the process's exit status. | |
| May 24 at 22:33 | history | became hot network question | |||
| May 24 at 22:01 | comment | added | waltinator | Put an event into the system's logs, too. Start by reading man logger rsyslog, and follow the "See Also" refs. | |
| May 24 at 20:03 | answer | added | grawity | timeline score: 11 | |
| May 24 at 14:36 | answer | added | Marcus Müller | timeline score: 9 | |
| S May 24 at 14:18 | review | First questions | |||
| May 24 at 14:46 | |||||
| S May 24 at 14:18 | history | asked | NightFuryLxD | CC BY-SA 4.0 |