From: Christopher Howard <christopher@librehacker.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Stefan Kangas <stefankangas@gmail.com>, 74855-done@debbugs.gnu.org
Subject: bug#74855: 30.0.92; dired - slow copy across (wireless) LAN
Date: Thu, 19 Dec 2024 07:59:51 -0900 [thread overview]
Message-ID: <874j2zvcag.fsf@librehacker.com> (raw)
In-Reply-To: <87ed23lwqh.fsf@gmx.de> (Michael Albinus's message of "Thu, 19 Dec 2024 12:48:22 +0100")
Michael Albinus <michael.albinus@gmx.de> writes:
> Tramp's "ssh" method is not suited for this use case. It encodes the
> local file with base64, and decodes it when it has been arrived on the
> remote side.
>
> For this given use case, Tramp's "scp" method is better suited. See the
> discussion in the manual, (info "(tramp) Connection types") and (info
> "(tramp) Frequently Asked Questions") , the entry "How to speed up TRAMP".
Okay, thank you. I switched to "scp" method and it was much faster. Somehow I didn't realize or remember that there was a separate Tramp info manual, but I will spend more time studying that.
--
Christopher Howard
next prev parent reply other threads:[~2024-12-19 16:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 16:37 bug#74855: 30.0.92; dired - slow copy across (wireless) LAN Christopher Howard
2024-12-19 4:31 ` Stefan Kangas
2024-12-19 11:48 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-19 16:59 ` Christopher Howard [this message]
2024-12-19 17:50 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-19 17:58 ` Stefan Kangas
2024-12-19 18:53 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-19 20:14 ` Stefan Kangas
2024-12-19 22:27 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-19 23:02 ` Christopher Howard
2024-12-19 23:09 ` Stefan Kangas
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=874j2zvcag.fsf@librehacker.com \
--to=christopher@librehacker.com \
--cc=74855-done@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=stefankangas@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.