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: Tue, 04 Jan 2022 17:25:29 +0100 [thread overview]
Message-ID: <87iluz79ja.fsf@elite.giraud> (raw)
In-Reply-To: <87czl77j7e.fsf@gmx.de> (Michael Albinus's message of "Tue, 04 Jan 2022 13:56:37 +0100")
Michael Albinus <michael.albinus@gmx.de> writes:
[...]
> Tramp tries this if possible. See the function tramp-do-copy-or-rename-file,
> which calls tramp-do-copy-or-rename-file-directly. This happens in two
> cases:
Hi Michael,
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)
>> Same question for two different hosts: Is it possible to make tramp do a
>> scp from host A to host B directly?
>
> Not (yet). See the TODO section at the end of tramp-sh.el:
>
> ;; * Optimize out-of-band copying when both methods are scp-like (not
> rsync).
Ok, i'll look that up. You said "Not (yet)": I've you already started
some work on it?
I have in my init a (simple) function that does this out-of-band scp but
I think that the most tricky parts (for something general pupose) are:
- how host A understand host B name?
- is host B reachable from host A?
… this kind of things.
Best regards,
--
Manuel Giraud
next prev parent reply other threads:[~2022-01-04 16:25 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 [this message]
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
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=87iluz79ja.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).