From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Eli Zaretskii <eliz@gnu.org>, Ken Brown <kbrown@cornell.edu>,
emacs-devel@gnu.org
Subject: Re: Reading D-Bus messages
Date: Fri, 24 Sep 2010 16:28:14 +0200 [thread overview]
Message-ID: <4C9CB57E.1010708@swipnet.se> (raw)
In-Reply-To: <871v8jhcw2.fsf@gmx.de>
2010-09-24 08:30, Michael Albinus skrev:
> Eli Zaretskii<eliz@gnu.org> writes:
>
>> 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?
>
> D-Bus messages arrive asynchronously. xd_read_queued_messages() converts
> them into special events, which are stored via kbd_buffer_store_event().
>
> gobble_input() is used, because it is called at several places, for
> instance in sit_for(), kbd_buffer_get_event(), get_input_pending(),
> ns_select() - D-Bus messages shall be handled as soon as they arrive.
>
This is overkill. Not even X messages are processed this fast.
Checking for D-bus messages when the input loop is entered should be enough.
Jan D.
next prev parent reply other threads:[~2010-09-24 14:28 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 [this message]
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
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=4C9CB57E.1010708@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kbrown@cornell.edu \
--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).