From: Wolfgang Jenkner <wjenkner@inode.at>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: emacs-devel@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
Dima Kogan <dima@secretsauce.net>
Subject: Re: gfile-based file notifications are not immediate
Date: Wed, 29 Oct 2014 15:00:23 +0100 [thread overview]
Message-ID: <851tprvuvc.fsf@iznogoud.viz> (raw)
In-Reply-To: 87ioj3m6ah.fsf@gmx.de
On Wed, Oct 29 2014, Michael Albinus wrote:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>> Interesting. Another point in favor of dropping inotify support,
>
> There are people who do not want glib linked with Emacs.
Also, glib is part of GNOME, which, as a whole, does not seem to be
interested in systems which are not commercially relevant for them.
There's an active project to implement inotify for *BSD
https://github.com/dmatveev/libinotify-kqueue
While it still lacks inotify_init1, a year or so ago I worked around
this by some voodoo and built emacs to use the library. That basically
worked (and, IIRC, even passed the inotify-test.el of the time) but in
some situations removing a watch did not work correctly and a cpu core
remained pegged at maximum usage while emacs was running.
So, in the long run, inotify might be the more portable solution.
Wolfgang
next prev parent reply other threads:[~2014-10-29 14:00 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-25 20:17 gfile-based file notifications are not immediate Dima Kogan
2014-10-26 7:55 ` Michael Albinus
2014-10-26 13:12 ` Ken Brown
2014-10-28 21:33 ` Rüdiger Sonderfeld
2014-10-29 1:06 ` Stefan Monnier
2014-10-29 2:23 ` Dima Kogan
2014-10-29 3:54 ` Stefan Monnier
2014-10-29 12:03 ` Michael Albinus
2014-10-29 13:56 ` Stefan Monnier
2014-10-29 14:11 ` Óscar Fuentes
2014-10-29 15:29 ` Stefan Monnier
2014-10-29 16:28 ` Michael Albinus
2014-10-29 20:34 ` Stefan Monnier
2014-10-30 15:16 ` Perry E. Metzger
2014-10-30 16:51 ` Stefan Monnier
2014-10-30 17:10 ` Perry E. Metzger
2014-10-30 17:40 ` Michael Albinus
2014-10-30 18:04 ` Perry E. Metzger
2014-10-30 18:06 ` Stefan Monnier
2014-10-30 18:11 ` Michael Albinus
2014-10-30 19:21 ` Perry E. Metzger
2014-10-30 19:39 ` Dima Kogan
2014-10-30 19:27 ` Stefan Monnier
2014-10-29 14:00 ` Wolfgang Jenkner [this message]
2014-10-30 19:12 ` Wolfgang Jenkner
2014-10-30 20:32 ` Rüdiger Sonderfeld
2014-10-31 21:28 ` Perry E. Metzger
2014-11-02 14:15 ` Noam Postavsky
2014-11-02 15:50 ` Perry E. Metzger
2014-10-26 16:02 ` Eli Zaretskii
2014-10-26 17:07 ` Dima Kogan
2014-10-26 17:14 ` Eli Zaretskii
2014-10-26 16:41 ` Michael Albinus
2014-10-28 0:32 ` Dima Kogan
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=851tprvuvc.fsf@iznogoud.viz \
--to=wjenkner@inode.at \
--cc=dima@secretsauce.net \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=monnier@iro.umontreal.ca \
/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).