Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
config:all_you_never_wanted_to_know_about_file_saving [2013/05/06 20:44] – add proper title colombanwconfig:all_you_never_wanted_to_know_about_file_saving [2019/05/28 05:38] (current) – gio_unsafe_save_backup vstepaniuk
Line 41: Line 41:
   * Uses Geany's own code so it can be modified.   * Uses Geany's own code so it can be modified.
  
-If use_atomic_file_saving is set, use_gio_file_saving is ignored and Geany will use an atomic file save method.  This means that the file is first written to a temporary file, then renamed to the existing file name.  On most file systems rename is atomic, that is it succeeds completely or nothing will change, especially on modern journalling systems.  This functionality is provided and maintained by the Glib library.+If use_atomic_file_saving is set, use_gio_unsafe_file_saving is ignored and Geany will use an atomic file save method.  This means that the file is first written to a temporary file, then renamed to the existing file name.  On most file systems rename is atomic, that is it succeeds completely or nothing will change, especially on modern journalling systems.  This functionality is provided and maintained by the Glib library.
  
 Advantages: Advantages:
Line 75: Line 75:
 Disadvantages: 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.**+  * There is a [[https://bugzilla.gnome.org/show_bug.cgi?id=602412|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.   * 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.   * Uses twice the disk space.
Line 95: Line 95:
 Disadvantages: Disadvantages:
  
-  * Only works if use_gio_unsafe_file_saving is in operation, remember use_atomic_file_saving overrides it.+  * Only works if ''use_gio_unsafe_file_saving'' is in enabled and ''use_atomic_file_saving'' is disabled (''use_atomic_file_saving'' **overrides** ''use_gio_unsafe_file_saving'').
   * Uses twice the disk space.   * Uses twice the disk space.
   * Can be slow on remote filesystems as it may have to read and write data to create the backup if renaming fails.   * Can be slow on remote filesystems as it may have to read and write data to create the backup if renaming fails.

Trace:

Print/export