From: Michael Albinus <michael.albinus@gmx.de>
To: James Cloos <cloos@jhcloos.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: Using glib's g_file_monitor_file and g_file_monitor_directory
Date: Wed, 03 Apr 2013 21:55:07 +0200 [thread overview]
Message-ID: <87a9pfpexw.fsf@gmx.de> (raw)
In-Reply-To: <m3eherctdi.fsf@carbon.jhcloos.org> (James Cloos's message of "Wed, 03 Apr 2013 15:21:20 -0400")
James Cloos <cloos@jhcloos.com> writes:
> SM> AFAIK Emacs almost always links to glib indirectly nowadays, so it
> SM> would probably be OK to replace the inotify version with the glib
> SM> version.
>
> Please don't. Not every box where emacs is used runs x11, and glib
> should not be a forced dependency. Inotify(7) support is welcome
> even on headless systems.
It shall be configurable. Glib's implementation might the primary
choice, pure inotify the second choice, and none of them the third
one. Except systems which use w32notify, of course.
I'll try to prepare a patch before my vacations (starting later in
April).
I will also think about a unified Lisp interface for the different file
notification implementations. During the discussion last autumn, there
was a proposal (by Oscar? by Eli?) to distinguish between "file contents
changes" and "file metadata changes". This sounds to me like a good
starting point, abstracting from the different events raised by those
notification packages.
And of course, respective file name handlers and there needs shall not
be forgotten.
> -JimC
Best regards, Michael.
next prev parent reply other threads:[~2013-04-03 19:55 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 20:40 Using glib's g_file_monitor_file and g_file_monitor_directory Michael Albinus
2013-03-21 14:06 ` Ted Zlatanov
2013-03-21 14:54 ` Michael Albinus
2013-03-21 16:05 ` Ted Zlatanov
2013-03-22 7:52 ` Michael Albinus
2013-04-01 11:36 ` Michael Albinus
2013-04-01 17:50 ` Jan Djärv
2013-04-03 18:12 ` Stefan Monnier
2013-04-03 19:21 ` James Cloos
2013-04-03 19:36 ` Eli Zaretskii
2013-04-03 20:46 ` James Cloos
2013-04-03 19:55 ` Michael Albinus [this message]
2013-04-03 19:58 ` James Cloos
2013-04-04 0:49 ` Stefan Monnier
2013-05-28 10:39 ` Michael Albinus
2013-05-28 14:44 ` Paul Eggert
2013-05-28 15:33 ` Eli Zaretskii
2013-05-28 16:02 ` Paul Eggert
2013-05-28 16:21 ` Stefan Monnier
2013-05-28 16:45 ` Eli Zaretskii
2013-05-28 18:19 ` Stefan Monnier
2013-05-29 13:46 ` Michael Albinus
2013-05-29 14:03 ` Stefan Monnier
2013-05-29 14:09 ` Michael Albinus
2013-05-29 17:40 ` Stefan Monnier
2013-05-30 14:09 ` Michael Albinus
2013-05-30 21:08 ` Stefan Monnier
2013-05-28 16:43 ` Eli Zaretskii
2013-05-28 16:52 ` Paul Eggert
2013-05-28 16:59 ` Eli Zaretskii
2013-05-28 19:32 ` Paul Eggert
2013-05-28 15:58 ` Michael Albinus
2013-05-28 19:04 ` Paul Eggert
2013-05-28 20:31 ` Michael Albinus
2013-05-28 20:38 ` Paul Eggert
2013-05-29 6:12 ` Michael Albinus
2013-05-28 15:29 ` Eli Zaretskii
2013-05-29 13:30 ` Michael Albinus
2013-05-29 15:25 ` Eli Zaretskii
2013-05-29 15:57 ` Michael Albinus
2013-05-30 20:15 ` Daniel Colascione
2013-05-31 6:38 ` Michael Albinus
2013-06-02 16:57 ` Eli Zaretskii
2013-06-03 13:21 ` Michael Albinus
2013-06-03 15:12 ` Eli Zaretskii
2013-06-03 15:30 ` Glenn Morris
2013-06-03 16:29 ` Eli Zaretskii
2013-06-03 17:04 ` Eli Zaretskii
2013-06-03 17:27 ` Glenn Morris
2013-06-03 19:41 ` Michael Albinus
2013-06-04 6:09 ` Paul Eggert
2013-06-05 13:25 ` Michael Albinus
2013-06-05 18:37 ` Jan Djärv
2013-06-06 11:06 ` Michael Albinus
2013-06-07 10:53 ` Jan Djärv
2013-06-07 12:18 ` Michael Albinus
2013-06-07 14:22 ` Jan Djärv
2013-06-07 14:50 ` Michael Albinus
2013-06-08 8:50 ` Jan Djärv
2013-06-04 6:45 ` Paul Eggert
2013-06-04 15:16 ` Eli Zaretskii
2013-06-04 15:50 ` Paul Eggert
2013-06-05 1:23 ` Stefan Monnier
2013-06-06 7:10 ` Paul Eggert
2013-06-03 19:10 ` Michael Albinus
2013-05-30 11:11 ` Ken Brown
2013-05-28 15:30 ` Eli Zaretskii
2013-05-29 13:31 ` 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=87a9pfpexw.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=cloos@jhcloos.com \
--cc=emacs-devel@gnu.org \
--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).