From: Ken Brown <kbrown@cornell.edu>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: "Jan Djärv" <jan.h.d@swipnet.se>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Reading D-Bus messages
Date: Mon, 27 Sep 2010 22:47:34 -0400 [thread overview]
Message-ID: <4CA15746.9090806@cornell.edu> (raw)
In-Reply-To: <878w2mzxqp.fsf@gmx.de>
On 9/27/2010 5:23 PM, Michael Albinus wrote:
> Ken Brown<kbrown@cornell.edu> writes:
>
>> To finish off the Cygwin issue that started this thread, dbus now
>> works fine in emacs-24 under Cygwin, but not in emacs-23. Would
>> anyone object if I were to apply the following patch to the emacs-23
>> branch to fix the (Cygwin-specific) problem there?
>>
>> === modified file 'src/keyboard.c'
>> --- src/keyboard.c 2010-07-05 17:16:59 +0000
>> +++ src/keyboard.c 2010-09-27 19:33:05 +0000
>> @@ -4107,7 +4107,7 @@
>> interrupt handlers have not read it, read it now. */
>>
>> /* Note SIGIO has been undef'd if FIONREAD is missing. */
>> -#ifdef SIGIO
>> +#if defined (SIGIO) || defined (CYGWIN)
>> gobble_input (0);
>> #endif /* SIGIO */
>> if (kbd_fetch_ptr != kbd_store_ptr)
>
> Likely it is sufficient to move the call of xd_read_queued_messages out
> of gobble_input:
>
> --8<---------------cut here---------------start------------->8---
> *** ~/src/emacs-23/src/keyboard.c.~100064~ 2010-09-27 23:18:30.840864838 +0200
> --- ~/src/emacs-23/src/keyboard.c 2010-09-27 23:18:01.942112064 +0200
> ***************
> *** 4106,4111 ****
> --- 4106,4116 ----
> /* One way or another, wait until input is available; then, if
> interrupt handlers have not read it, read it now. */
>
> + #ifdef HAVE_DBUS
> + /* Read D-Bus messages. */
> + xd_read_queued_messages ();
> + #endif /* HAVE_DBUS */
> +
> /* Note SIGIO has been undef'd if FIONREAD is missing. */
> #ifdef SIGIO
> gobble_input (0);
> ***************
> *** 7051,7061 ****
> gobble_input (expected)
> int expected;
> {
> - #ifdef HAVE_DBUS
> - /* Read D-Bus messages. */
> - xd_read_queued_messages ();
> - #endif /* HAVE_DBUS */
> -
> #ifdef SIGIO
> if (interrupt_input)
> {
> --- 7056,7061 ----
> --8<---------------cut here---------------end--------------->8---
This works for me. Maybe you should test it too when you get a chance
and then check it in if you're satisfied.
Ken
next prev parent reply other threads:[~2010-09-28 2:47 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 [this message]
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
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
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=4CA15746.9090806@cornell.edu \
--to=kbrown@cornell.edu \
--cc=emacs-devel@gnu.org \
--cc=jan.h.d@swipnet.se \
--cc=michael.albinus@gmx.de \
/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).