Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Geany does not disable the GIO behaviour, it simply does not use GIO code to save if the setting is false
This is a bad news for me; so, no way to get rid of this because the application developers write the GIO code into their apps. I suppose in case of Geany the choice is only possible because there are other options for saving. The only solution is to not use GTK applications. (Except Geany which gives the user the freedom of choice.) But I remember that formerly this "GIO saving" was not used, no '.goutputstream-' files were created. The "evolution"...
Why would you disable this on the first place?
I do not want any swap file, backup file ... be created, because they are unnecessary and harmful for envorinment. Unnecessary because if in 10.000 cases there are 1 case with a problem that is not a tragedy. That 1 case does not justify the other 99.999 totally unnecessary writes. And those unnecessary writes means use of energy and hardware wear .i.e. destruction of nature. And if you say that this does not matter since it is a very little energy and hardware wear ... you are wrong: these "little nothings" are made by millions; that is it makes a huge difference globally. Similar stupidity (wrong for nature) is that now not the noatime option is the default mount option in Linux kernel.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.