@codebrainz we could, but that would mean using the GIO API only, never ever paths or anything like it. The whole mess about file saving so well documented by @elextr would be reduced to the g_file_replace_contents(), with its pros and cons.

@b4n This is what we already do when use_gio_unsafe_file_saving=TRUE since #621 (well, for the edited files only, not for Geany config files etc. but there's no point using GIO for those) - this is why I asked what settings @mf0hka is using.

Now in my opinion the "unsafe" in the name is a bit unfortunate - it's much less unsafe than it may seem from the name and people might be disabling it because of it. The second unfortunate thing is there are 4 combinations of

use_atomic_file_saving
use_gio_unsafe_file_saving

but just 3 different settings. Finally, the value isn't related to "saving" only any more - it determines the operations used both for opening and saving.

So it would be better to have a single entry in Various for this, something like "file_access_mode" with a dropdown containing 3 values - "GIO", "atomic", "POSIX", defaulting to "GIO" (I'd mention the unsafeness in the documentation with some more discussion but not directly in the mode name).

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