From: Eli Zaretskii <eliz@gnu.org>
To: sbaugh@catern.com
Cc: luangruo@yahoo.com, sbaugh@janestreet.com, 64423@debbugs.gnu.org
Subject: bug#64423: 29.0.92; save-interprogram-paste-before-kill doesn't prevent streaming large selections
Date: Tue, 04 Jul 2023 20:02:19 +0300 [thread overview]
Message-ID: <83y1jvk3tw.fsf@gnu.org> (raw)
In-Reply-To: <87h6qjoc6y.fsf@catern.com> (sbaugh@catern.com)
> From: sbaugh@catern.com
> Date: Tue, 04 Jul 2023 16:48:06 +0000 (UTC)
> Cc: luangruo@yahoo.com, sbaugh@janestreet.com, 64423@debbugs.gnu.org
>
> Eli Zaretskii <eliz@gnu.org> writes:
> > You cannot "make Emacs more concurrent", not by and large. We can
> > make small improvements here and there, if we tread cautiously and do
> > careful damage control after each such change, but that's all.
>
> That's all I ask for, the ability to make such small, careful, cautious
> improvements.
We seem to differ in what we call "small" improvements...
> > If you look at the low-level code in Emacs and take time to understand
> > how it works, you will agree with me. (And if you don't agree, we
> > will have this very argument again many times in the future.) We
> > should accept that fact, and either live with it or start a
> > new-generation Emacs, based on very different designs. Anything else
> > is just lying to ourselves.
>
> I've stared at low-level code in Emacs a good amount, but certainly I
> wouldn't claim to understand Emacs yet. Nevertheless...
>
> I think Lisp threads shows that this is not true.
If what I said were indeed not true, Lisp threads would have been a
hot feature, used by every package out there. That it is not so
should teach us something. I don't know if you tried to write a
serious application based on Lisp threads, but if not, maybe you
should try.
next prev parent reply other threads:[~2023-07-04 17:02 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 14:13 bug#64423: 29.0.92; save-interprogram-paste-before-kill doesn't prevent streaming large selections sbaugh
2023-07-03 2:35 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-03 12:46 ` Spencer Baugh
2023-07-04 0:40 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-04 1:45 ` sbaugh
2023-07-04 3:58 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-04 11:46 ` sbaugh
2023-07-04 13:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-04 14:46 ` sbaugh
2023-07-04 16:18 ` Eli Zaretskii
2023-07-04 16:32 ` Ihor Radchenko
2023-07-04 16:41 ` Eli Zaretskii
2023-07-04 16:48 ` sbaugh
2023-07-04 17:02 ` Eli Zaretskii [this message]
2023-07-04 17:14 ` Ihor Radchenko
2023-07-04 17:30 ` Eli Zaretskii
2023-07-04 17:35 ` Ihor Radchenko
2023-07-05 0:30 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-05 2:29 ` Eli Zaretskii
2023-07-05 3:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-05 11:27 ` Eli Zaretskii
2023-07-05 0:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-05 13:59 ` Spencer Baugh
2023-07-06 0:12 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-06 0:50 ` Spencer Baugh
2023-07-06 1:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-08 16:39 ` sbaugh
2023-07-08 16:48 ` Eli Zaretskii
2023-07-08 17:07 ` Spencer Baugh
2023-07-08 17:49 ` Eli Zaretskii
2023-07-09 0:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-09 6:10 ` Eli Zaretskii
2023-07-09 6:12 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-09 6:46 ` Eli Zaretskii
2023-07-12 19:18 ` sbaugh
2023-07-13 0:32 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-13 4:48 ` Eli Zaretskii
2023-07-13 16:17 ` sbaugh
2023-07-13 18:39 ` Eli Zaretskii
2023-07-13 22:39 ` sbaugh
2023-07-15 8:31 ` Eli Zaretskii
2023-07-15 8:33 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-15 9:01 ` Eli Zaretskii
2023-07-15 9:35 ` Eli Zaretskii
2023-07-15 17:38 ` sbaugh
2023-07-15 19:12 ` Eli Zaretskii
2023-07-15 21:00 ` Spencer Baugh
2023-07-17 16:43 ` Mattias Engdegård
2023-08-03 15:53 ` Spencer Baugh
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=83y1jvk3tw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64423@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=sbaugh@catern.com \
--cc=sbaugh@janestreet.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).