[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Reading D-Bus messages
From: |
Michael Albinus |
Subject: |
Reading D-Bus messages |
Date: |
Wed, 12 Aug 2009 11:43:37 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) |
Hi,
D-Bus messages are arriving to Emacs asynchronously. Unfortunately, there
is no trigger mechanism which notifies the arrival of a message; one must
poll for new incoming messages via dbus_connection_read_write().
The call of this method is wrapped by xd_read_queued_messages() of
dbusbind.c, which is called in gobble_input() (see keyboard.c). D-Bus
messages are converted into Emacs events, and stored via
kbd_buffer_store_event().
This works fine, as long as Emacs runs in a window manager. redisplay()
runs periodically, which includes reading the D-Bus messages.
When Emacs is started in a terminal, this does not work anymore. The
input handling seems to wait for keyboard interrupts and alike, and does
NOT poll anymore, whether there are other incoming events.
How shall xd_read_queued_messages() be activated in such a case?
Best regards, Michael.
- Reading D-Bus messages,
Michael Albinus <=
- Re: Reading D-Bus messages, YAMAMOTO Mitsuharu, 2009/08/12
- Re: Reading D-Bus messages, Michael Albinus, 2009/08/12
- Re: Reading D-Bus messages, YAMAMOTO Mitsuharu, 2009/08/12
- Re: Reading D-Bus messages, Michael Albinus, 2009/08/15
- Re: Reading D-Bus messages, YAMAMOTO Mitsuharu, 2009/08/15
- Re: Reading D-Bus messages, Michael Albinus, 2009/08/16
- Re: Reading D-Bus messages, YAMAMOTO Mitsuharu, 2009/08/16
- Re: Reading D-Bus messages, Daniel Pittman, 2009/08/17
- Re: Reading D-Bus messages, Michael Albinus, 2009/08/18