From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 37573@debbugs.gnu.org, tim.zander@kit.edu
Subject: bug#37573: 27.0.50; Remote file opened from GNOME-Nautilus
Date: Mon, 07 Oct 2019 19:28:17 +0300 [thread overview]
Message-ID: <83r23ozfj2.fsf@gnu.org> (raw)
In-Reply-To: <87r23pat27.fsf@gmx.de> (message from Michael Albinus on Mon, 07 Oct 2019 09:55:12 +0200)
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: tim.zander@kit.edu, 37573@debbugs.gnu.org
> Date: Mon, 07 Oct 2019 09:55:12 +0200
>
> I've tested the scenario (editing a remote file from Nautilus via Emacs)
> with GVFS volumes of different types. ftp and afp-volume work w/o
> problems. ssh/sftp behaves as reported (problem with file locking).
>
> dav(s), google-drive and smb-share give another error:
>
> Error: (file-error "Doing chmod" "Operation not supported" "/run/user/1000/gvfs/smb-share:server=detlef,share=netlogon/tmp/tramp-test1H01tS")
>
> So it doesn't make sense to implement the workaround in general. What we
> could do instead is to map all files under "/run/user/%d/gvfs" to the
> respective Tramp file name. Don't know whether it is worth the effort.
>
> After all, I believe we shall simply document the behavior, and the
> workaround for ssh/sftp.
If we cannot fix this, then documenting sounds good to me. In
etc/PROBLEMS, perhaps?
next prev parent reply other threads:[~2019-10-07 16:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 15:00 bug#37573: 27.0.50; Remote file opened from GNOME-Nautilus Tim Zander
2019-10-06 10:37 ` Michael Albinus
2019-10-06 17:44 ` Eli Zaretskii
2019-10-07 7:55 ` Michael Albinus
2019-10-07 16:28 ` Eli Zaretskii [this message]
2019-10-08 12:57 ` Michael Albinus
2019-10-08 13:11 ` Eli Zaretskii
2019-10-08 13:44 ` Michael Albinus
2019-10-08 14:15 ` Tim Zander
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83r23ozfj2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=37573@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=tim.zander@kit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).