From: Michael Albinus <michael.albinus@gmx.de>
To: Dima Kogan <dima@secretsauce.net>
Cc: 18958@debbugs.gnu.org
Subject: bug#18958: 25.0.50; auto-revert-mode reacts slowly even if using an event-driven backend
Date: Tue, 24 Feb 2015 09:42:18 +0100 [thread overview]
Message-ID: <87vbirr991.fsf@gmx.de> (raw)
In-Reply-To: <87a9049zhk.fsf@secretsauce.net> (Dima Kogan's message of "Mon, 23 Feb 2015 11:51:56 -0800")
Dima Kogan <dima@secretsauce.net> writes:
>> I meant gfilenotify is superior to inotify wrt file notifications due to
>> its polling feature. That does not mean auto-revert, since Emacs has its
>> own polling mechanism here.
>
> Ah, ok. This is true. Would you be opposed to setting the default to
> "inotify" on Linux since this currently provides a better user
> experience there?
I believe this was discussed already back in 2013, when I've contributed
gfilenotify.c. I cannot find the emails, likely there's something in the
archives.
What's the default must be decided by Stefan anyway, as the Emacs
maintainer. Personally, I can live with this 1sec delay of glib. And
glib is linked to Emacs also for other reasons, if not configured off.
Maybe it's better to discuss this on emacs-devel, but in this bug.
Best regards, Michael.
prev parent reply other threads:[~2015-02-24 8:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 19:01 bug#18958: 25.0.50; auto-revert-mode reacts slowly even if using an event-driven backend Dima Kogan
2014-11-07 20:01 ` Stefan Monnier
2015-02-19 20:41 ` Michael Albinus
2015-02-20 9:59 ` Dima Kogan
2015-02-20 10:25 ` Michael Albinus
2015-02-21 3:38 ` Dima Kogan
2015-02-21 9:57 ` Michael Albinus
2015-02-21 11:39 ` Eli Zaretskii
2015-02-21 12:43 ` Michael Albinus
2015-02-28 15:31 ` Eli Zaretskii
2015-02-21 22:38 ` Dima Kogan
2015-02-22 9:53 ` Michael Albinus
2015-02-22 15:57 ` Eli Zaretskii
2015-02-23 3:47 ` Dima Kogan
2015-02-23 16:05 ` Michael Albinus
2015-02-23 19:51 ` Dima Kogan
2015-02-24 8:42 ` Michael Albinus [this message]
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=87vbirr991.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=18958@debbugs.gnu.org \
--cc=dima@secretsauce.net \
/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).