Olhando Geany wiki , parece que você pode também precisa desativar esta opção:
use_gio_unsafe_file_saving
This is on by the default, and is provided by the GIO library.
This option attempts to deal with as many of the issues associated with the other methods as it can:
- It attempts to use the atomic rename saving method described above, but tries to address as many issues as it can:
- it checks metadata of the temporary file and tries to copy the metadata from the existing file,
- if the metadata is correct, it writes to the temporary and renames as above,
- if the metadata is not correct, it uses a non-atomic but safe method of:
- copying the existing file to a temporary file
- truncating and overwriting the existing file, if this fails the temporary file should be copied back or available, but see disadvantages below.
- It attempts to determine if rename is available on the underlying file system, and uses the non-atomic method if rename fails.
Advantages:
- Deals with the most different conditions, so works the most correctly on the most file systems. That is why it is the default.
Disadvantages:
- There is a long standing bug or design fault in the GIO library that deletes the temporary file from the non-atomic save if writing the data file fails. This means it is no more safe than the simple overwrite method since the previous data is not restored, or even left available for the user to restore.
- The non-atomic save copies data over the network three times (read and write to make the temporary file, write the output file) which can be slow on remote networks.
- Uses twice the disk space.
- Is quite complex.
- Uses library code so Geany can't modify its behaviour
Que método estranho de salvar arquivos. Parece que pode resultar na mesma economia "atômica" que a opção use_atomic_file_saving
.