Comment 4 for bug 227808

gvim sftp://leann@leann//home/leann/bug.txt

Yes, this will not produce the error because gvim will connect to the remote "real" file system directly through sftp. The error only happens when going through the gvfs/fuse file system.

Further thinking about it, I think this bug comes from two places. First, why does vim chmod files when it saves them? Other text editors don't do this. Perhaps a vim patch is necessary?

Second, how come all files in the gvfs/fuse file system have permissions of either 600 or 700? What if someone wants to make a script in the gvfs/fuse file system executable? What if someone wants to allow a web server to deliver files from a gvfs/fuse file system? These things are not possible if all permissions are defaulted to 600/700 and all chmods are passed through to the underlying "true" file system (at least with sftp they are).

I think there needs to be a fundamental change to the way gvfs/fuse deals with file permissions.