From: Ken Brown <kbrown@cornell.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Reading D-Bus messages
Date: Fri, 24 Sep 2010 09:20:45 -0400 [thread overview]
Message-ID: <4C9CA5AD.1030707@cornell.edu> (raw)
In-Reply-To: <83tylgtbo8.fsf@gnu.org>
On 9/23/2010 5:03 PM, Eli Zaretskii wrote:
>> Date: Thu, 23 Sep 2010 16:49:32 -0400
>> From: Ken Brown<kbrown@cornell.edu>
>> Cc: emacs-devel<emacs-devel@gnu.org>
>>
>>>> Do you understand why gobble_input is called only if SIGIO is defined?
>>>
>>> Don't know. ChangeLog.1 says:
>>>
>>> 1986-01-23 Richard M. Stallman (rms@prep)
>>>
>>> * dispnew.c (Fsit_for):
>>> Call gobble_input only if SIGIO exists.
>>>
>>> 1985-11-01 Richard M. Stallman (rms@prep)
>>>
>>> * keyboard.c (gobble_input, input_available_signal,
>>> kbd_buffer_store_char):
>>> Make these functions exist only if SIGIO is defined.
>>>
>>> 1985-10-16 Richard M. Stallman (rms@mit-prep)
>>>
>>> * keyboard.c:
>>> Get error instead of croaking if want to send SIGTSTP.
>>> Get compile time error in gobble_input if SIGIO is not
>>> defined.
>>
>> Well, I'll just try it for a while and see if I notice any problems as a
>> result of using gobble_input without SIGIO. If not, I'll upload a new
>> Cygwin test release and see what happens.
>
> I'd rather turn the table and ask why is the call to
> xd_read_queued_messages made in gobble_input and not elsewhere? Why
> are we mixing input from D-Bus with keyboard input? And why in
> gobble_input?
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. Is this
something that was needed in 1985 and is no longer relevant?
Ken
next prev parent reply other threads:[~2010-09-24 13:20 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 13:18 Reading D-Bus messages Michael Albinus
2010-09-22 18:21 ` Ken Brown
2010-09-23 7:19 ` Michael Albinus
2010-09-23 12:16 ` Ken Brown
2010-09-23 13:42 ` Michael Albinus
2010-09-23 14:26 ` Ken Brown
2010-09-23 14:46 ` Michael Albinus
2010-09-23 20:49 ` Ken Brown
2010-09-23 21:03 ` Eli Zaretskii
2010-09-24 6:30 ` Michael Albinus
2010-09-24 8:18 ` Eli Zaretskii
2010-09-24 11:24 ` Michael Albinus
2010-09-24 14:28 ` Jan Djärv
2010-09-24 15:10 ` Michael Albinus
2010-09-24 15:31 ` Eli Zaretskii
2010-09-24 21:11 ` Michael Albinus
2010-09-25 7:19 ` Jan Djärv
2010-09-25 16:52 ` Michael Albinus
2010-09-25 18:04 ` Jan Djärv
2010-09-25 20:54 ` Michael Albinus
2010-09-26 16:31 ` Jan Djärv
2010-09-26 18:24 ` Ken Brown
2010-09-26 18:38 ` Michael Albinus
2010-09-26 19:17 ` Jan Djärv
2010-09-27 15:37 ` Michael Albinus
2010-09-27 19:36 ` Ken Brown
2010-09-27 21:23 ` Michael Albinus
2010-09-28 2:47 ` Ken Brown
2010-09-28 13:47 ` Michael Albinus
2010-09-25 21:46 ` Ken Brown
2010-09-26 0:51 ` Ken Brown
2010-09-26 6:43 ` Michael Albinus
2010-09-24 13:20 ` Ken Brown [this message]
2010-09-24 13:24 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2009-08-12 9:43 Michael Albinus
2009-08-12 10:18 ` YAMAMOTO Mitsuharu
2009-08-12 10:43 ` Michael Albinus
2009-08-12 11:47 ` YAMAMOTO Mitsuharu
2009-08-15 19:16 ` Michael Albinus
2009-08-16 0:09 ` YAMAMOTO Mitsuharu
2009-08-16 12:30 ` Michael Albinus
2009-08-17 1:33 ` YAMAMOTO Mitsuharu
2009-08-17 4:05 ` Daniel Pittman
2009-08-18 15:24 ` Michael Albinus
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C9CA5AD.1030707@cornell.edu \
--to=kbrown@cornell.edu \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.