unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: File watch support in autorevert.el
Date: Fri, 11 Jan 2013 23:47:41 +0100	[thread overview]
Message-ID: <87libz2v76.fsf@gmx.de> (raw)
In-Reply-To: <jwv1udr65dn.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 11 Jan 2013 11:44:09 -0500")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> Will do for the inotify case. It is a simple bit easier, because you can
>> install a file watch for exactly one file, and you can expect it returns
>> for that file only.
>
> BTW, what happens if the file gets overwritten without touching its
> inode (e.g. use auto-revert-mode on ~/foo and then do "mv ~/bar ~/foo"
> and then "echo toto >>~/foo")?
>
> You'll presumably get some notification of the "mv" itself, but will you
> subsequently get the notification of the "echo" (which is now modifying
> another inode than the original ~/foo)?

No further notifications. I've realized it just now, because this is the
scenario when you save a file with `backup-by-copying' set to nil. You
will loose further notifications, because the file was moved away.

Tested in the inotify case. For w32notify, I don't know.

>         Stefan

Best regards, Michael.



  reply	other threads:[~2013-01-11 22:47 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-10 14:28 File watch support in autorevert.el Michael Albinus
2013-01-10 17:11 ` Stefan Monnier
2013-01-10 17:14   ` Lennart Borgman
2013-01-10 20:38   ` Michael Albinus
2013-01-11 10:05 ` Eli Zaretskii
2013-01-11 14:34   ` Stefan Monnier
2013-01-11 14:43     ` Eli Zaretskii
2013-01-11 15:01       ` Michael Albinus
2013-01-11 15:50         ` Eli Zaretskii
2013-01-11 16:09           ` Michael Albinus
2013-01-11 19:19             ` Eli Zaretskii
2013-01-11 16:19           ` Michael Albinus
2013-01-11 16:39         ` Stefan Monnier
2013-01-11 22:43           ` Michael Albinus
2013-01-12 11:28             ` Eli Zaretskii
2013-01-12 13:34               ` Michael Albinus
2013-01-12 15:09                 ` Eli Zaretskii
2013-01-12 19:08                   ` Michael Albinus
2013-01-17  9:38                   ` Michael Albinus
2013-01-17 16:54                     ` Eli Zaretskii
2013-01-17 19:19                       ` Michael Albinus
2013-01-17 19:39                         ` Eli Zaretskii
2013-01-11 15:57       ` Stefan Monnier
2013-01-11 15:18   ` Michael Albinus
2013-01-11 15:57     ` Eli Zaretskii
2013-01-11 16:31       ` Michael Albinus
2013-01-11 18:47         ` Eli Zaretskii
2013-01-11 16:44     ` Stefan Monnier
2013-01-11 22:47       ` Michael Albinus [this message]
2013-01-12 11:36         ` Eli Zaretskii
2013-01-12 13:14           ` Michael Albinus
2013-01-12 14:06             ` Eli Zaretskii
2013-01-12 14:16               ` Michael Albinus
2013-01-11 22:39   ` Michael Albinus
2013-01-11 23:01   ` Michael Albinus
2013-01-12 11:31     ` Eli Zaretskii
2013-01-12 13:08       ` Michael Albinus
2013-01-12 13:26         ` Michael Albinus
2013-01-12 14:03         ` Eli Zaretskii
2013-01-12 14:12           ` Michael Albinus
2013-01-12 14:39             ` Eli Zaretskii
2013-01-12 19:04               ` 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=87libz2v76.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=eliz@gnu.org \
    --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).