From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 16519@debbugs.gnu.org
Subject: bug#16519: 24.3.50; gfile notifications not received in batch mode
Date: Fri, 31 Jan 2014 17:00:18 +0100 [thread overview]
Message-ID: <87k3dggmzx.fsf@gmx.de> (raw)
In-Reply-To: <83r47o5gg7.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 31 Jan 2014 17:17:12 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> Maybe we should have ert-sit-for, then, which does everything like
> sit-for, except relying on input-pending-p?
There is ert-async.el <https://github.com/rejeep/ert-async.el>. I like
this idea, although the timer loop applies only
accept-process-output. read-event shall be added, at least.
Maybe we should contact the author, whether he agrees to merge this code
into ert.el?
>> I remember. I've added the !HAVE_DBUS prepocessor statetements due to
>> Bug#11415. It was a similar situation, D-Bus events were not read in
>> batch mode. So we really need a changed handling of special events in
>> the main loop, instead of adding more preprocessor lines.
>
> I don't see why we would need a separate queue for special events.
> What we need, perhaps, is a way to peek at stdin to see whether
> there's some input ready to be gobbled. Shouldn't select/pselect
> already provide that? IOW, there should be no need to call getchar at
> all at this point.
Reading file notifications via gio does not use file descriptors, which
are handled via xg_select. The same will happen, if we switch to gdbus
or kdbus later on. That's why we might need another kind of mainloop integration.
I'm not too familiar with kbd_buffer_store_event and the mechanisms
behind. If we still could use them - OK.
Best regards, Michael.
next prev parent reply other threads:[~2014-01-31 16:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-09 14:35 bug#13662: 24.3.50; inotify-add-watch fails in batch mode Chong Yidong
2014-01-17 11:56 ` Michael Albinus
2014-01-25 14:16 ` Eli Zaretskii
2014-01-26 15:55 ` Michael Albinus
2014-01-26 16:09 ` bug#16519: 24.3.50; gfile notifications not received " Michael Albinus
2014-01-26 17:43 ` Michael Albinus
2014-01-27 16:08 ` Michael Albinus
2014-01-29 18:14 ` Eli Zaretskii
2014-01-30 10:03 ` Michael Albinus
2014-01-30 17:03 ` Eli Zaretskii
2014-01-31 14:11 ` Michael Albinus
2014-01-31 15:17 ` Eli Zaretskii
2014-01-31 16:00 ` Michael Albinus [this message]
2014-01-31 16:53 ` Eli Zaretskii
2014-02-03 13:31 ` Michael Albinus
2014-02-03 16:13 ` Eli Zaretskii
2014-02-04 11:43 ` Michael Albinus
-- strict thread matches above, loose matches on Subject: below --
2014-01-22 9:50 Michael Albinus
2014-01-22 15:49 ` Eli Zaretskii
2014-01-24 11:23 ` 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=87k3dggmzx.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=16519@debbugs.gnu.org \
--cc=eliz@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.