From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: master 54b9213: Handle thread-signal towards the main thread (Bug#32502)
Date: Fri, 07 Sep 2018 08:12:31 -0400 [thread overview]
Message-ID: <jwv8t4dse3m.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83y3cdvp2a.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 07 Sep 2018 08:45:01 +0300")
>> Hmm... would people really be OK with --without-threads causing Gnus to
>> become unusable?
> If Gnus indeed is unusable without threads (I didn't know that),
It's not the case (yet), but it would be helpful to treat such
a situation as a non-bug, so that Gnus can be modified to take advantage
of threads without having to worry about backward compatibility.
> that could be a bug in Gnus that should be fixed.
Yet we wouldn't consider it a bug in Calc if it doesn't work when we
build without bignums. That's the difference between bignums and
threads currently, and the point of my original question is to ask
whether we could change this situation and decide that Emacs-27 will
always come with threads, just like it always comes with bignums.
Stefan
next prev parent reply other threads:[~2018-09-07 12:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180830192912.24309.93190@vcs0.savannah.gnu.org>
[not found] ` <20180830192914.85ECE20497@vcs0.savannah.gnu.org>
2018-08-30 21:40 ` master 54b9213: Handle thread-signal towards the main thread (Bug#32502) Glenn Morris
2018-08-31 7:09 ` Michael Albinus
2018-09-05 18:00 ` Glenn Morris
2018-09-06 6:58 ` Michael Albinus
2018-09-06 12:25 ` Stefan Monnier
2018-09-06 14:23 ` Eli Zaretskii
2018-09-06 14:32 ` Stefan Monnier
2018-09-06 18:18 ` Eli Zaretskii
2018-09-06 19:52 ` Stefan Monnier
2018-09-07 5:45 ` Eli Zaretskii
2018-09-07 12:12 ` Stefan Monnier [this message]
2018-09-07 13:45 ` Eli Zaretskii
2018-09-07 14:13 ` Stefan Monnier
2018-09-07 16:17 ` Eric Abrahamsen
2018-09-07 20:53 ` Michael Albinus
2018-09-08 15:48 ` Eric Abrahamsen
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=jwv8t4dse3m.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).