From: Michael Albinus <michael.albinus@gmx.de>
To: Nicolas Petton <nicolas@petton.fr>
Cc: 30946@debbugs.gnu.org
Subject: bug#30946: 26.0.90; TRAMP cannot access some files when using hops
Date: Thu, 29 Mar 2018 16:11:02 +0200 [thread overview]
Message-ID: <87sh8j9dl5.fsf@gmx.de> (raw)
In-Reply-To: <87o9jbfcsc.fsf@petton.fr> (Nicolas Petton's message of "Mon, 26 Mar 2018 10:42:43 +0200")
Nicolas Petton <nicolas@petton.fr> writes:
Hi Nicolas,
> As discussed on the emacs-devel mailing list, when using tramp with
> multiple hops like the following:
>
> C-x C-f /ssh:me@example.com|sudo:localhost:/etc/deluser.conf
>
> Tramp opens an empty buffer, without showing any error message.
>
> I understand now that the second hop should be "sudo:example.com:", but
> it felt intuitive to use localhost, and for most files on the remote
> host it actually worked.
I have added an additional check in Tramp for host name matches in such
cases. This checks also the single hop case "/sudo:example.com:", which
shall fail when "example.com" is not your local host name.
There's a new test case for this, tramp-test03-file-name-host-rules. I
have the feeling that this test needs too much time; maybe I'll move it
to the expensive tests.
Could you pls check, whether Tramp behaves now as expected?
Best regards, Michael.
next prev parent reply other threads:[~2018-03-29 14:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 8:42 bug#30946: 26.0.90; TRAMP cannot access some files when using hops Nicolas Petton
2018-03-29 14:11 ` Michael Albinus [this message]
2018-04-03 12:02 ` Nicolas Petton
[not found] ` <6e181a50-452c-0e8b-ae5a-0746f64a6dfb@orcon.net.nz>
2018-12-30 22:01 ` Phil Sainty
2018-12-31 11:20 ` Michael Albinus
2018-12-31 12:40 ` Phil Sainty
2018-12-31 14:13 ` Michael Albinus
2018-12-31 21:48 ` Phil Sainty
2019-01-01 11:54 ` Michael Albinus
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=87sh8j9dl5.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=30946@debbugs.gnu.org \
--cc=nicolas@petton.fr \
/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).