unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Jordan Wilson <jordan.t.wilson@gmx.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Issues with multi-hop in TRAMP
Date: Sat, 16 Feb 2019 17:20:18 +0100	[thread overview]
Message-ID: <874l93d7st.fsf@gmx.de> (raw)
In-Reply-To: <8736on23an.fsf@gmx.com> (Jordan Wilson's message of "Sat, 16 Feb 2019 14:53:04 +0000")

Jordan Wilson <jordan.t.wilson@gmx.com> writes:

> Hi Michael,

Hi Jordan,

> On 2019-02-16 (Sat) at 09:51 (+0100), Michael Albinus <michael.albinus@gmx.de> wrote:
>> Have you tried sole "/plink:username@machine:"?
> They work fine. No problems connecting to that machine with plink.

Fine.

>> Do you use packages which keep information over Emacs sessions, like
>> recentf.el or desktop.el?
> I use recentf.el. It can see in `recentf-open-files' files retrieved
> using that multi-hop are labelled like
> "/sshx:username@machine2:/home/jordan/hello.txt"

Well, that's the problem. Multi-hop remote files, as you use them, are
called "ad-hoc". The reason is that this syntax is intended for the
moment, and not suited to survive Emacs sessions. Tramp reduces the file
name "/method1:host1|method2:host2:" to "/method2:host2", just for
convenience. The needed hop for host2 is kept internally during the
Emacs session.

When you open a new Emacs session, and recentf reads its initial file
with the shortened file name, this information is lost.

So you shall either declare multi-hop by means of
`tramp-default-proxies-alist' (see the Tramp manual, node "Multi-hops"),
or you shall set `tramp-save-ad-hoc-proxies' to t (see the Tramp manual,
node "Ad-hoc multi-hops"), which stores that information persistently.

Anyway, it is an error in recentf to store such shortened remote file
name, missing the ad-hoc multi-hop information. I will check, whether
this could be fixed.

(Maybe you write an Emacs bug report about, in order not to forget? I
cannot promise that I will work on this just now.)

> But even if that was somehow the cause, that doesn't
> explain why this issue appears in "emacs -Q".

Indeed, I also don't know what's up with "emacs -Q" here. To be
investigated as well.

> Regards,

Best regards, Michael.



  reply	other threads:[~2019-02-16 16:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-14 19:48 Issues with multi-hop in TRAMP Jordan Wilson
2019-02-15  9:52 ` Michael Albinus
2019-02-16  0:10   ` Jordan Wilson
2019-02-16  8:51     ` Michael Albinus
2019-02-16 14:53       ` Jordan Wilson
2019-02-16 16:20         ` Michael Albinus [this message]
2019-02-25 11:52           ` 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=874l93d7st.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=help-gnu-emacs@gnu.org \
    --cc=jordan.t.wilson@gmx.com \
    /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.
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).