unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dima Kogan <dima@secretsauce.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: gfile-based file notifications are not immediate
Date: Sun, 26 Oct 2014 10:07:26 -0700	[thread overview]
Message-ID: <87k33mg3l9.fsf@secretsauce.net> (raw)
In-Reply-To: <83mw8i4y52.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Dima Kogan <lists@dima.secretsauce.net>
>> Date: Sat, 25 Oct 2014 13:17:29 -0700
>> 
>> As in the inotify thread, I set up a simple test. I built emacs using
>> 
>>  ./configure --with-file-notification=inotify
>> 
> Maybe I'm confused, but are you saying that even though you
> specifically requested for inotify notifications, and even though the
> configure script shows
>
>   Does Emacs use a file notification library?       yes -lglibc (inotify)

Ack! My first email in this thread had a massive error. The intent was
for this thread to be about gfile-based file notifications, so the
configure wass done with

 ./configure --with-file-notification=gfile

Sorry about the unnecessary confusion. Hope the message makes more sense
now.



  reply	other threads:[~2014-10-26 17:07 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
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 [this message]
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=87k33mg3l9.fsf@secretsauce.net \
    --to=dima@secretsauce.net \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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).