In reply to #25, I believe the reason it happens with gvim but not gedit is because gedit natively supports opening files via gvfs, whereas gvim doesn't and so it gets passed the "~/.gvfs" path, but the permissions are not exposed correctly there. I do not know if this is intentional or a bug, but it is making it very hard to use gvfs for making remote edits (to configs etc.) with gvim. I'm also currently using sshfs/fuse as a workaround, but I have to manually mount things so I hope I'll one day be able to just use gvim/gvfs.
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/227808 Title: file permissions destroyed by vim/gvfs/fuse To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/227808/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
