Ah HA!

use_atomic_file_saving ... Disadvantages: ... Because it writes the temporary file as a new file, it will get the permissions and other metadata (eg execute) of a new file, not those of the old file.

Thank you.

You did notice that either of the other saving methods should keep the x bit at the cost of loss of guaranteed atomicity?

Well the default is `use_gio_unsafe_file_saving` so we endorse it in most cases, precisely because it handles metadata and Windows filesystems that won't rename, so for most people it "just works" :smile:

The "unsafe" only applies when something goes wrong, which for local storage is either the device breaks, or the partition is full, both of which "should" be very rare (but some people seem to try to eke the last byte out their storage so maybe full is less rare). And so long as the loss of the device/partition doesn't stop the system or Geany the advice in the wiki applies, `don't panic` the buffer is still in memory, save it somewhere else eg a USB key.