I think you missed the point of the use-case I was describing, to save the changes in the Geany buffer, not to protect files already on disk. All the points you make about the file being safe are irrelevant because the contents of the Geany buffer have not been saved to a file yet. The use-case of Autosave I am describing is to save the buffer contents periodically in case Geany or the system crashes.

And that list is just ways the file can be removed without the user deliberately and explicitly deleting it. If they deleted it then sure they probably don't want the changed buffer saved, at least not under that name. But with all the other ways the file can be inadvertently removed the need for the periodic save remains.

"Contributions" doesn't just mean you, other people may have thoughts to add. As you correctly point out a useful first "contribution" would be suggestions for a suitable design, since this is not a simple issue involving as it does asynchronous external operations, variable timing between autosave and Geany file checks, and several (potentially competing) use-cases.

—
Reply to this email directly or view it on GitHub.