That user has asked for autosave so they don't lose their latest changes because they are testing software that might crash Geany or the system. ... it could have been a side effect of a Version Control checkout, a rename, a build, or for a remote file a glitch in the network, or it might be a result of the some bug. ...

I do not agree with all the examples you mention above:

Version control checkout: Keeping files safe is a mission of source control. Source control will not overwrite your working files if they are changed. If they are not changed and overwritten than means they are already saved in VCS and safe.

Rename: If file renamed, user have the file, but under another name. Content is safe.

Build: If a file overwritten during build, that means it is a secondary file which was built form source files, and can be rebuilt again if needed.

Network problem: If a file is located on remote server and network is not reliable, it would be unwise to try to save it again in the same location because saving will likely fail. If you want to keep such a file safe, save it on local drive.

To me for keeping files safe "Backup Copy" should be used, not "Auto Save". Let it save backup copies not every "normal" save but every N seconds + in other emergency cases. Backup copies are created in dedicated directory, so if Geany saves a copy of intentionally deleted file in that dedicated directory, it will not irritate the user.

I managed to hit a timing that caused a sequence of five dialogs/infobars ...

Did you try to delete several files? You will have much more questions...

What is needed is for autosave to keep an exclusion list of files/directories it won't try to autosave so it won't simply ask again every n seconds. So I have changed this to an enhancement request. Contributions are welcome.

What do you mean under "contribution"? Fix in Geany code? We do not have understanding and agreement on the topic, so I do not think my contribution will be really welcome. BTW, submitting bugs is contribution, too.

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