Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
just a regular session closure
A session closure is a crash as far as any running applications are concerned, they get sent a SIGTERM (and if they don't exit fast enough a SIGKILL) they don't get shutdown politely.
Geany used to try to save files when it received a SIGTERM, but that has a dialog and user interaction, illegal actions in a SIGTERM handler, and user interaction was often too slow. So the whole thing was undefined behaviour from performing illegal actions in a signal handler, and random success depending on how fast the user was, and increased risk of losing the original files as the risk of being killed during writing was increased. So that was disabled.
As to the message, for string contents just use the pencil to edit it in github, since you don't have permission github will kindly go to the trouble of making you a fork and submitting a PR.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.