[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RFC] Gnus generalized search, part II

From: Eli Zaretskii
Subject: Re: [RFC] Gnus generalized search, part II
Date: Sat, 22 Apr 2017 18:17:47 +0300

> From: Eric Abrahamsen <address@hidden>
> Date: Sat, 22 Apr 2017 08:08:05 -0700
> Eli Zaretskii <address@hidden> writes:
> >> From: Eric Abrahamsen <address@hidden>
> >> 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.

But what _is_ the right thing?

I asked the question because I really would like to know what would
you want/expect to be the effect of C-g on the active threads?  It's
not a rhetoric question.  Can you please humor me?

> Is (accept-process-output 0) the same as (accept-process-output
> nil)?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]