From: Eli Zaretskii <eliz@gnu.org>
To: joakim@verona.se
Cc: yandros@gmail.com, arthur.miller@live.com, emacs-tangents@gnu.org
Subject: Re: Shrinking the C core
Date: Tue, 12 Sep 2023 22:42:02 +0300 [thread overview]
Message-ID: <83pm2nnppx.fsf@gnu.org> (raw)
In-Reply-To: <878r9b8b2a.fsf@tanaka.verona.se> (joakim@verona.se)
> X-Spam-Status: No, score=-1.01 tagged_above=-999 required=6.2
> tests=[ALL_TRUSTED=-1, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=disabled
> From: joakim@verona.se
> Cc: Eli Zaretskii <eliz@gnu.org>, Arthur Miller <arthur.miller@live.com>,
> emacs-tangents@gnu.org
> Date: Tue, 12 Sep 2023 21:07:41 +0200
>
> - if I'm connected to an emacs session by ssh, and mistakenly make a
> cli command dump tens of megabytes of spewage to the shell buffer, I'm in trouble
> and cant easily get out of it. I need to open a new ssh session and
> kill the rampaging cli. This is quite tedious. Would concurrency fix this?
This should be doable, and doesn't come anywhere near the "rewrite"
job. You just need a way of blocking the output from the shell, and
then use Emacs commands to kill it.
> - Same for long-lines, this is still not a solved problem.
You didn't try Emacs 29 yet, did you?
> - Gnus refreshes slowly, maybe that could be helped with concurrency,
> but it could also be helped with more async work in gnus.
Concurrency can help you keep reading messages while Gnus refreshes in
parallel, but it won't easily help you refresh faster, unless someone
comes up with a way of collecting the update in parallel chunks (in
which case they should be able to do that today with the emacs-async
package, I think).
next prev parent reply other threads:[~2023-09-12 19:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AM9PR09MB497796E739349F8CB9AD4F4996F1A@AM9PR09MB4977.eurprd09.prod.outlook.com>
2023-09-12 11:55 ` Shrinking the C core Eli Zaretskii
2023-09-12 18:22 ` chad
2023-09-12 18:47 ` Yuri Khan
2023-09-12 19:06 ` Eli Zaretskii
2023-09-12 19:07 ` joakim
2023-09-12 19:42 ` Eli Zaretskii [this message]
2023-09-12 21:56 ` joakim
2023-09-13 5:05 ` Emanuel Berg
2023-09-13 14:29 ` joakim
2023-09-15 5:46 ` Emanuel Berg
2023-09-13 15:33 ` Fraga, Eric
2023-09-15 5:51 ` Emanuel Berg
2023-09-15 11:38 ` Fraga, Eric
2023-09-13 5:06 Arthur Miller
2023-09-13 6:33 ` Gerd Möllmann
2023-09-14 11:35 ` Arthur Miller
2023-09-14 13:03 ` Gerd Möllmann
2023-09-14 13:20 ` Eli Zaretskii
2023-09-15 17:11 ` Emanuel Berg
2023-09-15 18:39 ` Eli Zaretskii
[not found] <AM9PR09MB4977E9C0FD5922D0291C4B0796F1A@AM9PR09MB4977.eurprd09.prod.outlook.com>
2023-09-12 11:29 ` Po Lu
[not found] <AM9PR09MB4977C010362EBF83BCF3491C96E0A@AM9PR09MB4977.eurprd09.prod.outlook.com>
[not found] ` <873503y66i.fsf@yahoo.com>
[not found] ` <AM9PR09MB49779854134CDC2E4FB2AD2996E0A@AM9PR09MB4977.eurprd09.prod.outlook.com>
[not found] ` <E1qbX63-0003Ty-Rn@fencepost.gnu.org>
[not found] ` <E1qdgsR-0000j8-BN@fencepost.gnu.org>
[not found] ` <AM9PR09MB497757F8D921063E3D60D40C96EFA@AM9PR09MB4977.eurprd09.prod.outlook.com>
[not found] ` <ZPhih7q2ml8v6EfP@ACM>
[not found] ` <87bkeeoqf3.fsf@dataswamp.org>
[not found] ` <ZPl0+E1jYEJ2noRt@tuxteam.de>
[not found] ` <87wmx2mooq.fsf@dataswamp.org>
2023-09-07 7:52 ` tomas
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=83pm2nnppx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=arthur.miller@live.com \
--cc=emacs-tangents@gnu.org \
--cc=joakim@verona.se \
--cc=yandros@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.
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).