Ah yes those options. It somehow sparked an interest here so I decided to test behaviour (and increase my understanding) perhaps it is of use for others as well:
- | Gio backup | Use atomic | Use Gio | win10 | Ubuntu 17.04 | Notes -- | -- | -- | -- | -- | -- | -- Default | n | n | y | new file | preserve | test1 | y | n | y | new file [1] | preserve [2] | test2 | y | y | y | new file | new file | Should act as test7 test3 | n | y | y | new file | new file | Should act as test7 test4 | n | n | n | preserve | preserve | Point 1 test5 | y | n | n | preserve | preserve | Should act as test4 test6 | y | y | n | new file | new file | Should act as test7 test7 | n | y | n | new file | new file | Point 2
The *Should act as* comments are based on my understanding of the wiki information. The *Point* comments refer to expected behaviour from your points
The 1st observation I draw from this is that gio (it is a gtk library corrrect?) behaves differently on windows and linux. The 2nd observation is that my linux box does not behave as in your 3rd comment. If I understand that one correct the default behaviour should create a new file. However (luckily for me) it honours the link.
[1] link is renamed to link~ (but preserved as symbolic link) [2] link~ is a new file with old contents as described in wiki
note: Under windows I also ran tests with geany as admin to rule out any permission problems in (re)creating symbolic links. The results from those test were identical to the normal user, hence I omitted those.