From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Monnier <monnier@IRO.UMontreal.CA>, emacs-devel@gnu.org
Subject: Re: master 54b9213: Handle thread-signal towards the main thread (Bug#32502)
Date: Fri, 07 Sep 2018 09:17:51 -0700 [thread overview]
Message-ID: <87sh2lcmds.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <83y3cdvp2a.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 07 Sep 2018 08:45:01 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Stefan Monnier <monnier@IRO.UMontreal.CA>
>> Date: Thu, 06 Sep 2018 15:52:21 -0400
>> Cc: emacs-devel@gnu.org
>>
>> >> Cool, then let's remove --without-threads,
>> > That's a separate issue. AFAIU, this option exists for people who
>> > don't want threads in Emacs even if they can be supported.
>>
>> 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), that
> could be a bug in Gnus that should be fixed.
FWIW, my idea here (and someone else might get around to implementing
this before I do, so this might be meaningless) was to let each Gnus
server conduct each network access in its a separate thread. So not a
single "Gnus thread", nor even "one thread per server", but creating a
new thread for each server as it accesses the network, letting the
thread then return and die. So once we have a canonical check for thread
support, it wouldn't be hard to accommodate both situations.
next prev parent reply other threads:[~2018-09-07 16:17 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
2018-09-07 13:45 ` Eli Zaretskii
2018-09-07 14:13 ` Stefan Monnier
2018-09-07 16:17 ` Eric Abrahamsen [this message]
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=87sh2lcmds.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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).