From: "J.P." <jp@neverwas.me>
To: Alcor <alcor@tilde.club>
Cc: Alcor via General discussion about ERC <emacs-erc@gnu.org>,
69833@debbugs.gnu.org
Subject: bug#69833: 29.2; ERC 5.6-git: erc-dcc: Transmission of large (>500 MB) files hangs Emacs
Date: Sun, 17 Mar 2024 10:15:14 -0700 [thread overview]
Message-ID: <87zfuwsrtp.fsf__5820.48346275172$1710695822$gmane$org@neverwas.me> (raw)
In-Reply-To: <878r2hp59l.fsf@tilde.club> (alcor@tilde.club's message of "Sun, 17 Mar 2024 10:38:30 +0100")
Alcor <alcor@tilde.club> writes:
> Yes, I can confirm the solution from that ticket (#54458) works. Using
> "/dcc get -t", no problems are observed. Emacs remains responsive, and
> the CPU usage during the transfer is slightly lower, too.
>
> From what I understood, this is more of sender-specific issue, which is
> well-known. Let me know if a reproducible example is still needed, I can
> arrange something and send it off-list if necessary.
It may be worth looking into if you think we can somehow devine on the
fly whether the server's using turbo. Otherwise, I guess users will just
have to try both. Perhaps we should say something to that effect in the
doc string or the library ;;; Commentary? (Unfortunatly, ERC doesn't yet
have sections for individual modules in its documentation.)
> PS: Sorry for the noise, I did a debbugs search for "erc dcc" beforehand
> but it yielded no results.
Yeah, I haven't managed to make debbugs do my bidding either, so I just
download all the articles and index them locally (but maybe that's a
sucker's move?).
prev parent reply other threads:[~2024-03-17 17:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-16 18:02 bug#69833: 29.2; ERC 5.6-git: erc-dcc: Transmission of large (>500 MB) files hangs Emacs Alcor via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-17 0:03 ` J.P.
[not found] ` <871q89vi5o.fsf@neverwas.me>
2024-03-17 9:38 ` Alcor via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <878r2hp59l.fsf@tilde.club>
2024-03-17 17:15 ` J.P. [this message]
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='87zfuwsrtp.fsf__5820.48346275172$1710695822$gmane$org@neverwas.me' \
--to=jp@neverwas.me \
--cc=69833@debbugs.gnu.org \
--cc=alcor@tilde.club \
--cc=emacs-erc@gnu.org \
/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).