There is a setting `save_config_on_file_change` to prevent saves when files are opened/closed see https://www.geany.org/manual/current/index.html#id132, but the config will still be saved if you change any setting.
Configuration and sessions are intended to save the state at that point of time so it can be restarted, that is its use-case, and that use-case is not met if something goes wrong if its not saved. Having a message if the save fails is intended, to let the user know they may lose data (eg due to read-only config), but it does not prevent you editing, it is not a bug. There have been a number of reports of loss of session due to user action (eg logging out with Geany still running), system action (crashes) and Geany action (plugin crashes) and the only method to handle that is to save when something changes. There is an in-progress change to split the session files from the config which is being developed on the session_split branch. But I expect it will still save configuration whenever it changes, but the session changes will be in a different file. You could assist with that branch, or propose your own pull request with your feature, feature requests only happen when "somebody" does them. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2863#issuecomment-897201996
