[Github-comments] [geany/geany] Not honoring symbolic links on windows when saving (#1533)

R1dO notifications at xxxxx
Sat Jul 8 14:48:35 UTC 2017


Thank you

@codebrainz I did not have that plugin enabled. Before I did those tests the existing  ``.config/geany`` folder was moved out of the way so geany could recreate the default settings.

@elextr I totally misinterpreted your 3rd point then. To me it came across that gio would first use the atomic routine (even when not selected) and only try gio if the atomic is not able to recreate metadata.
As for the permissions (linux only, all i get from my limited windows Powershell knowledge is *Full Access*):
* The umask on the directory used during the tests was: ``0002``.
* Permissions on the link are: ``Access: (0777/lrwxrwxrwx)``
* Permissions on the target are ``Access: (0664/-rw-rw-r--)``
* Permissions on the backup file are ``Access: (0664/-rw-rw-r--)``

Derived from the comments in the Glib library I do believe that gio checks for and preserves the link. 
The writing routine ``[geany]\documents.c::write_data_to_disk()`` for atomic writes calls ``[glib]\ gfileutils.c::g_file_set_contents()`` this function warns about not preserving symlinks in the description.
That same routine for gio writes calls ``[glib]\gfile.c::g_file_replace_contents()`` this function (and callees) do not warn about this. 
Hence my (weak) conclusion that by default gio will preserve symlinks.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/1533#issuecomment-313860063
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.geany.org/pipermail/github-comments/attachments/20170708/a2ccc3a9/attachment.html>


More information about the Github-comments mailing list