From: Manuel Giraud <manuel@ledu-giraud.fr>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Dired command on same host
Date: Wed, 05 Jan 2022 10:44:03 +0100 [thread overview]
Message-ID: <8735m27c0s.fsf@elite.giraud> (raw)
In-Reply-To: <878rvv73mr.fsf@gmx.de> (Michael Albinus's message of "Tue, 04 Jan 2022 19:33:00 +0100")
Michael Albinus <michael.albinus@gmx.de> writes:
> Manuel Giraud <manuel@ledu-giraud.fr> writes:
>
>> Hi Michael,
>
> Hi Manuel,
>
>> Sorry my bad. Maybe my two dired buffers were not `tramp-equal-remote'
>> (BTW, I think there is a typo in the example of the docstring of
>> `tramp-equal-remote':
>>
>> Example:
>>
>> (tramp-equal-remote \"/ssh::/etc\" \"/-:<your host name>:/home\")
>> ^
>> |_ shouldn't
>> it be etc here)
>
> No. tramp-equal-remote ignores the local part of the remote file
> names. That's what the docstring says above the example.
Sorry again. I should read more carefully :-|
[...]
> Must be checked, yes. But this isn't a problem for Tramp. It keeps shell
> sessions on both host A and host B, a simple "ssh -q -o ConnectTimeout=1
> B exit 2>/dev/null" on host A would tell us whether host B is reachable
> (checking the exit code, and caching the result). If not, Tramp could
> fall back to the current behavior.
To adress Tassilo remark, maybe it should make a hash of «some known»
file too to ensure that this is the correct host B. Or maybe this is too
much.
--
Manuel Giraud
next prev parent reply other threads:[~2022-01-05 9:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 10:24 Dired command on same host Manuel Giraud
2022-01-04 12:56 ` Michael Albinus
2022-01-04 16:25 ` Manuel Giraud
2022-01-04 18:33 ` Michael Albinus
2022-01-04 19:35 ` Tassilo Horn
2022-01-05 9:35 ` Manuel Giraud
2022-01-05 21:07 ` Tomas Hlavaty
2022-01-06 11:01 ` Michael Albinus
2022-01-07 15:50 ` Michael Albinus
2022-01-10 9:33 ` Manuel Giraud
2022-01-10 12:56 ` Michael Albinus
2022-01-10 14:07 ` Manuel Giraud
2022-01-10 15:00 ` Michael Albinus
2022-01-10 16:16 ` Manuel Giraud
2022-01-11 8:25 ` Michael Albinus
2022-01-11 8:59 ` Manuel Giraud
2022-01-11 9:10 ` Michael Albinus
2022-01-10 17:21 ` Yuri Khan
2022-01-11 8:29 ` Michael Albinus
2022-01-05 10:34 ` Michael Albinus
2022-01-05 13:02 ` Manuel Giraud
2022-01-05 14:37 ` Michael Albinus
2022-01-05 18:23 ` Manuel Giraud
2022-01-05 9:44 ` Manuel Giraud [this message]
2022-01-05 10:40 ` Michael Albinus
2022-01-05 11:08 ` Yuri Khan
2022-01-05 11:46 ` Michael Albinus
2022-01-05 19:55 ` Tassilo Horn
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=8735m27c0s.fsf@elite.giraud \
--to=manuel@ledu-giraud.fr \
--cc=help-gnu-emacs@gnu.org \
--cc=michael.albinus@gmx.de \
/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).