You can set the atomic file saving setting (and only that one, see the wiki article) to get the best chance of avoiding data loss.

But the process that provides atomic file saving doesn't work everywhere (like on some network storage systems or windows systems) and it introduces other problems like ownership and protection issues.

Those issues are not a function of Geany or the library that provides the atomic write code, its the way the operating system works, and all other editors will have the same problem.

But these issues atomic save causes keep annoying users all the time, not just on the (should be) rare occasion that writing fails.

The GIO_unsafe option attempts to fix those issues, but the workarounds add complexity and risk of data loss because it may not be able to use the atomic save technique. But for most cases it "just works" and on most systems, and thats why its the default.

That's simple: data loss in a software must be avoided, period (excepted in case of hardware problems, of course).

To be clear, running out of disk part way through writing the file is a hardware problem. Your hardware doesn't have a big enough disk :)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.