Re: Reading D-Bus messages

[Michael Albinus <michael.albinus@gmx.de>]

YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp> writes:


> While Emacs is idle, it blocks at the select() call in
> wait_reading_process_output waiting for one of the several kinds of
> events to happen: window-system events, subprocess output arrivals,
> socket status changes, signal arrivals, and timer expirations.  That's
> why it is important to have a file/socket descriptor to monitor for
> D-Bus in order to avoid consuming CPU time for polling.

Finally, it was sufficient to add the D-Bus file descriptors via
add_keyboard_wait_descriptor. Thanks for pushing me into the right
direction!

> As far as I browsed some D-Bus documents,
> dbus_connection_set_watch_functions seems to have something to do with
> this.

DBusWatch uses its own select() loop. So it seems to be better to avoid it.

Mario, could you, please, check whether it works for you?

Best regards, Michael.