unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Sean McAfee <eefacm@gmail.com>
Cc: 20299@debbugs.gnu.org
Subject: bug#20299: 25.0.50; File notification is not working
Date: Sat, 11 Apr 2015 09:03:19 +0200	[thread overview]
Message-ID: <87egnrxi2w.fsf@gmx.de> (raw)
In-Reply-To: <CANan03b4zXaPeSXTYUZXDKkXUv0UUvgEtc-r-HmDAO-F9_kb6w@mail.gmail.com> (Sean McAfee's message of "Fri, 10 Apr 2015 17:39:48 -0700")

Sean McAfee <eefacm@gmail.com> writes:

Hi Sean,

> auto-revert-use-notify had a value of t, and yet
> auto-revert-notify-modified-p was nil even in buffers whose associated
> files had changed out from under them. I verified this visiting a
> file,
> then repeatedly issuing the shell command "echo foo >> my-file" and
> then
> evaluating the expression (auto-revert-handler) with M-:, but the file
> never got reverted.

On which directory have you done this? Note, that inotify does not work
on mounted directories.

> I can just set auto-revert-use-notify to nil going forward, but it
> would
> be nice to get file notification working as intended.

Another test you might apply is setting prior magit-auto-revert-mode

(require 'filenotify)
(require 'trace)
(dolist (elt (all-completions "file-notify-" obarray 'functionp))
  (trace-function (intern elt)))

You will observe in the buffer *trace-output*, whether file
notifications events arrive.

Best regards, Michael.





  reply	other threads:[~2015-04-11  7:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-11  0:39 bug#20299: 25.0.50; File notification is not working Sean McAfee
2015-04-11  7:03 ` Michael Albinus [this message]
     [not found]   ` <CANan03bo=meT7fQZ_QPxAgO69x_PBPx_H53BLMqUYk-=iqOybg@mail.gmail.com>
     [not found]     ` <87vbgyn8tr.fsf@gmx.de>
     [not found]       ` <CANan03ZDin3ZkU_=NxPa0Xyf2ouNrVYVJy7q-=Oo+Bo1Hs3KtQ@mail.gmail.com>
2015-04-16 14:25         ` Michael Albinus
2015-04-18 16:54           ` Sean McAfee
2015-04-18 17:51             ` Michael Albinus
2015-04-19  8:27               ` 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=87egnrxi2w.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=20299@debbugs.gnu.org \
    --cc=eefacm@gmail.com \
    /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).