unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Howard <christopher@librehacker.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Michael Albinus <michael.albinus@gmx.de>, 74855@debbugs.gnu.org
Subject: bug#74855: 30.0.92; dired - slow copy across (wireless) LAN
Date: Thu, 19 Dec 2024 14:02:06 -0900	[thread overview]
Message-ID: <878qsbb7kh.fsf@librehacker.com> (raw)
In-Reply-To: <CADwFkmm5WPuqpBXMZ7sCqV+Fc2wOeZdMo4CMk79urTUS2GiXVg@mail.gmail.com> (Stefan Kangas's message of "Thu, 19 Dec 2024 15:14:27 -0500")

Stefan Kangas <stefankangas@gmail.com> writes:

>> What would be the check? "A user wants to copy 600 files, with about 2GB
>> data total, via ssh"? Tramp doesn't know this, it works file-wise. Such a
>> check must reside in dired, but I still doubt we'll find a good rule.
>
> Something along those lines is what I imagined, yes.  The rule might not
> be perfect, but we could probably come up with some reasonable defaults
> if we thought about it.  But if it's not an interesting suggestion, then
> that's fine by me.

I don't think this is a critical issue, but another idea would be to simply have dired echo some kind of warning, suggesting to use the other method, and maybe referencing the manual.

The tricky part there, I think, is that the warning would get cleared from the echo area, by dired's progress messages, before the user had a chance to read or notice it. So I'm not sure if that would be useful in practice.

-- 
Christopher Howard





  parent reply	other threads:[~2024-12-19 23:02 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
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 [this message]
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

  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=878qsbb7kh.fsf@librehacker.com \
    --to=christopher@librehacker.com \
    --cc=74855@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 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).