From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 21241@debbugs.gnu.org, Tassilo Horn <tsdh@gnu.org>
Subject: bug#21241: 25.0.50; gfilenotify doesn't indicate when limits are reached
Date: Wed, 12 Aug 2015 21:18:45 +0200 [thread overview]
Message-ID: <87mvxw48oa.fsf@gmx.de> (raw)
In-Reply-To: <83zj1woamr.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 12 Aug 2015 17:16:12 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> > I wonder if we should revert our decision to prefer gfilenotify if
>> > available, and instead use it only if there's no other supported
>> > method. It begins to sound more and more like gfilenotify is more
>> > trouble than it's worth.
>>
>> You mean the other emacs-devel thread where it has been reported that
>> gfile notifications might get delayed up to 30 seconds?
>
> That, and this bug, and also the fact that it simply doesn't work on
> Windows (no notifications come in), although the corresponding glib
> tests all pass. There's also bug#20417, and I think someone also
> complained about gfilenotify on OS X.
I would also agree to favor inotify when available.
On OS X (better: on systems which have defined HAVE_NS), we should
disable gfilenotify, because the Glib main loop won't be used (ns_select
is used rather than xg_select).
Best regards, Michael.
next prev parent reply other threads:[~2015-08-12 19:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 8:16 bug#21241: 25.0.50; gfilenotify doesn't indicate when limits are reached Tassilo Horn
[not found] ` <handler.21241.B.14393674365819.ack@debbugs.gnu.org>
2015-08-12 8:34 ` Tassilo Horn
2015-08-12 12:47 ` Eli Zaretskii
2015-08-12 13:27 ` Tassilo Horn
2015-08-12 14:16 ` Eli Zaretskii
2015-08-12 19:18 ` Michael Albinus [this message]
2015-08-15 1:27 ` Paul Eggert
2015-08-18 14:33 ` Tassilo Horn
2015-08-18 17:09 ` Paul Eggert
2015-08-21 9:46 ` 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=87mvxw48oa.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=21241@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=tsdh@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 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).