From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-devel@gnu.org
Subject: Re: [RFC] Gnus generalized search, part II
Date: Sat, 22 Apr 2017 08:08:05 -0700 [thread overview]
Message-ID: <87inlw32ga.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 83efwkrhj1.fsf@gnu.org
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Eric Abrahamsen <eric@ericabrahamsen.net>
>> Date: Fri, 21 Apr 2017 22:27:45 -0700
>>
>> I don't know how threads interact with C-g.
>
> How would you want threads to interact with C-g?
I'm still trying to get a correct mental model of how all this is
working. I assume that, if I gather the threads using:
(mapc #'thread-join threads)
None of the threads ever become the "current thread", and so C-g would
only ever signal quit to the main thread. So maybe instead of mapc, we
do:
(dolist (t threads)
(condition-case nil
(thread-join t)
(quit (thread-signal t 'quit))))
According to my (limited, untested) understanding, that ought to do the
right thing.
While we're here, one more quick question. Gnus's IMAP servers collect
output by running this on a loop, until there's no more output:
(accept-process-output
(truncate nntp-read-timeout))
nntp-read-timeout is 0.1, and truncate turns that into 0. Is
(accept-process-output 0) the same as (accept-process-output nil)?
Thanks,
Eric
next prev parent reply other threads:[~2017-04-22 15:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 21:35 [RFC] Gnus generalized search, part II Eric Abrahamsen
2017-04-22 0:16 ` Andrew Cohen
2017-04-22 5:27 ` Eric Abrahamsen
2017-04-22 8:08 ` Eli Zaretskii
2017-04-22 15:08 ` Eric Abrahamsen [this message]
2017-04-22 15:17 ` Eli Zaretskii
2017-04-22 15:25 ` Eli Zaretskii
2017-04-22 19:25 ` Eric Abrahamsen
2017-04-22 20:06 ` Eli Zaretskii
2017-04-22 22:50 ` Eric Abrahamsen
2017-04-30 17:46 ` Eric Abrahamsen
2017-04-24 17:17 ` Stephen Leake
2017-04-26 9:42 ` Eli Zaretskii
2017-04-22 16:00 ` Noam Postavsky
2017-04-22 7:50 ` Eli Zaretskii
2017-04-22 8:00 ` Andrew Cohen
2017-04-22 19:53 ` Lars Ingebrigtsen
2017-04-22 20:26 ` Eric Abrahamsen
2017-04-24 20:30 ` Eric Abrahamsen
2017-04-26 4:41 ` Andrew Cohen
2017-04-26 9:21 ` Joakim Jalap
2017-04-26 8:18 ` Andrew Cohen
2017-04-26 8:22 ` Andrew Cohen
2017-04-23 13:48 ` Dan Christensen
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=87inlw32ga.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).