all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>,
	Tomas Hlavaty <tom@logand.com>,
	Manuel Giraud <manuel@ledu-giraud.fr>,
	Tassilo Horn <tsdh@gnu.org>
Subject: Re: Dired command on same host
Date: Tue, 11 Jan 2022 09:29:37 +0100	[thread overview]
Message-ID: <87ee5er7ym.fsf@gmx.de> (raw)
In-Reply-To: <CAP_d_8XtT2GAUOE_Gcs6tmU92kFT-Y0HMjLEYSxZvxRpwS4TMw@mail.gmail.com> (Yuri Khan's message of "Tue, 11 Jan 2022 00:21:14 +0700")

Yuri Khan <yuri.v.khan@gmail.com> writes:

>> Interesting. Honestly, I have no idea where the scp program buffers the
>> local temp data. Perhaps it is better to use this, indeed.
>
> Why would it have to buffer it anywhere? I can imagine it allocating a
> megabyte (or eight) of RAM, opening two network connections, then
> reading from one and writing to the other.

Perhaps. And perhaps, Tramp shall check and apply "-3" if
possible. Since OpenSSH 8.7, there seem to be more restrictions wrt
authentication. Quoting the man page:

--8<---------------cut here---------------start------------->8---
    -3      Copies between two remote hosts are transferred through the lo‐
             cal host.  Without this option the data is copied directly be‐
             tween the two remote hosts.  Note that, when using the legacy
             SCP protocol (the default), this option selects batch mode for
             the second host as scp cannot ask for passwords or passphrases
             for both hosts.  This mode is the default.
--8<---------------cut here---------------end--------------->8---



  reply	other threads:[~2022-01-11  8:29 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ee5er7ym.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=help-gnu-emacs@gnu.org \
    --cc=manuel@ledu-giraud.fr \
    --cc=tom@logand.com \
    --cc=tsdh@gnu.org \
    --cc=yuri.v.khan@gmail.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.