[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Reading D-Bus messages
From: |
Eli Zaretskii |
Subject: |
Re: Reading D-Bus messages |
Date: |
Fri, 24 Sep 2010 15:24:38 +0200 |
> Date: Fri, 24 Sep 2010 09:20:45 -0400
> From: Ken Brown <address@hidden>
> CC: emacs-devel <address@hidden>
>
> Regardless of what decision is ultimately made about these questions,
> I'd still like to know why one (and only one) of the calls to
> gobble_input in keyboard.c is made only if SIGIO is defined.
Because SIGIO means input is interrupt-driven, and therefore can
arrive asynchronously, by raising an interrupt and invoking the
interrupt handler. The other possibilities are synchronous, and
therefore don't need to be checked more than once in a loop.
- Re: Reading D-Bus messages, (continued)
- Re: Reading D-Bus messages, Jan Djärv, 2010/09/26
- Re: Reading D-Bus messages, Michael Albinus, 2010/09/27
- Re: Reading D-Bus messages, Ken Brown, 2010/09/27
- Re: Reading D-Bus messages, Michael Albinus, 2010/09/27
- Re: Reading D-Bus messages, Ken Brown, 2010/09/27
- Re: Reading D-Bus messages, Michael Albinus, 2010/09/28
- Re: Reading D-Bus messages, Ken Brown, 2010/09/25
- Re: Reading D-Bus messages, Ken Brown, 2010/09/25
- Re: Reading D-Bus messages, Michael Albinus, 2010/09/26
- Re: Reading D-Bus messages, Ken Brown, 2010/09/24
- Re: Reading D-Bus messages,
Eli Zaretskii <=