Improve way of handling Exceptions/Errors

[rzw]

Many issues here are about (explainable) crashes or program terminations. I would challenge the rationale behind the abrupt termination of the program upon all sorts of actions just because a user had done something external to the program. Wouldn't it be possible to just throw a message unable to... with a "try again" or cancel button. And if cancel is chosen just go back to the previous state. Even if the cause can't immediately be resolved it would at least be possible to copy edits to clipboard for pasting later or after a restart.

[TheJackiMonster]

Well, as the name says exceptions or errors are exactly that. If we would expect them to come up, they wouldn't really be what they are, right? Also it's not trivial to handle any kind of error inside of a more complex routine. Let's say out of 3 steps, the second fails throwing an error, you would still need to reverse the first step to cancel the routine. However it's not trivial to reverse any kind of function.

I think it should always be priority to fix errors or exceptions if possible. Next best thing is to avoid them. Only if none of this is possible, you need to handle them.