unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: File watch support in autorevert.el
Date: Sat, 12 Jan 2013 13:28:36 +0200	[thread overview]
Message-ID: <838v7ytzbv.fsf@gnu.org> (raw)
In-Reply-To: <87pq1b2vdf.fsf@gmx.de>

> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: Eli Zaretskii <eliz@gnu.org>,  emacs-devel@gnu.org
> Date: Fri, 11 Jan 2013 23:43:56 +0100
> 
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
> 
> > Try:
> >
> >   while sleep 60; do echo hello; done >> ~/tmp/123
> >
> > Look ma, no close!
> >
> > But you don't need a script: just try auto-revert-mode on a log written
> > by syslogd.
> >
> > Admittedly, these cases are presumably clients of auto-revert-tail-mode,
> > but auto-revert-mode should handle them correctly.
> 
> Should be OK now for all 3 modes: global-auto-revert-mode,
> auto-revert-mode and auto-revert-tail-mode (support for the last one is
> just committed). For the inotify case, I've changed to IN_MODIFY as
> supervised event. For w32notify, I have added size as proposed by Eli.

Thanks.  I tried auto-revert-mode and auto-revert-tail-mode on
MS-Windows, and they both seem to work as expected (after I fixed the
minor issues described in my other mail).

I see only one problem: if you manually "M-x revert-buffer RET", a new
file watch is added, although the old one is still active.  AFAICS,
you rely on the watch descriptor local var be non-nil for avoiding
this, so perhaps revert-buffer reverts that variable as well?  Or is
this a Windows-only problem?



  reply	other threads:[~2013-01-12 11:28 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 [this message]
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
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=838v7ytzbv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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).