From: Michael Albinus <michael.albinus@gmx.de>
To: Aleksei Fedotov <aleksei@fedotov.email>
Cc: 53223-done@debbugs.gnu.org
Subject: bug#53223: 27.2; multi-hop TRAMP with find-file-visit-truename t
Date: Wed, 23 Feb 2022 09:40:43 +0100 [thread overview]
Message-ID: <87ee3u7z78.fsf@gmx.de> (raw)
In-Reply-To: <87mtjzz2fl.fsf@gmx.de> (Michael Albinus's message of "Thu, 13 Jan 2022 23:38:38 +0100")
Michael Albinus <michael.albinus@gmx.de> writes:
Hi Aleksei,
>> It works exactly as described in the documentaion, but what is bothering me is
>> the difference in behaviour depending on the state of
>> `find-file-visit-truename'. It should only affect symlink resolution, but it
>> also changes Tramp behaviour.
>>
>> If `find-file-visit-truename' is set to nil, then Tramp is able to revert the
>> buffer and add a multi-hop definition back to `tramp-default-proxies-alist'.
>> If `find-file-visit-truename' is set to t, then it doesn't work. Shouldn't the
>> buffer somehow preserve the full path?
>
> It isn't just a find-file-visit-truename problem. Tramp cleans up ad-hoc
> multi-hop proxies when tramp-cleanup-all-connections is performed. This
> could happen for many different Tramp file name operations, not just
> file truenames. It is sheer luck for you that the example works when you
> haven't set find-file-visit-truename.
>
> If you replace tramp-cleanup-all-connections by tramp-cleanup-this-connection
> in your example, it works as expected.
No further comment, so I close this bug.
Best regards, Michael.
prev parent reply other threads:[~2022-02-23 8:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 21:23 bug#53223: 27.2; multi-hop TRAMP with find-file-visit-truename t Aleksei Fedotov
2022-01-13 14:00 ` Michael Albinus
2022-01-13 20:54 ` Aleksei Fedotov
2022-01-13 22:38 ` Michael Albinus
2022-02-23 8:40 ` Michael Albinus [this message]
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=87ee3u7z78.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=53223-done@debbugs.gnu.org \
--cc=aleksei@fedotov.email \
/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).