all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Antoine Levitt <antoine.levitt@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: lennart.borgman@gmail.com, joakim@verona.se, emacs-devel@gnu.org
Subject: Re: Emacs inotify support?
Date: Sat, 12 Sep 2009 18:36:47 +0200	[thread overview]
Message-ID: <6fa54e4e0909120936s24634600sf00a818aabd308ce@mail.gmail.com> (raw)
In-Reply-To: <83tyz8z3sl.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1628 bytes --]

2009/9/12 Lennart Borgman <lennart.borgman@gmail.com>
>
> On Sat, Sep 12, 2009 at 12:54 AM, Antoine Levitt
> <antoine.levitt@gmail.com> wrote:
> > and what would happen on very frequently modified
> > files (ie would I be able to view a log file without being flooded by
> > notifications).
>
> Is not this a case when you want notifications?
>
Imagine a log file on a web server, when there is a new line each second.
With a naïve implementation (current dialog each time the file changes), you
wouldn't be able to do anything because notifications would be too frequent.



> > Date: Sat, 12 Sep 2009 00:54:50 +0200
> > From: Antoine Levitt <antoine.levitt@gmail.com>
> > Cc: joakim@verona.se, Emacs Development <emacs-devel@gnu.org>
> >
> > if a user has a buffer open with some file
> > and that file changes outside emacs, he won't be notified of changes
until
> > he actually tries to modify it. Ideal case : emacs would monitor every
file
> > used by buffers, and notify of changes with the current dialog
(continue,
> > refresh, etc) in visible buffers.
>
> This use-case does not need any help from the OS to implement the
> feature in Emacs.  It should be quite easy to write a function that
> runs off the idle timer and checks each file that Emacs visits.
>
> The OP was talking about detecting changes in files that Emacs does
> not know about, including in files that are created while Emacs runs.

Indeed. If possible, polling should be avoided, though. And if inotify
or similar notification systems are implemented, it would be easy to
support both files and directories.

[-- Attachment #2: Type: text/html, Size: 2461 bytes --]

  reply	other threads:[~2009-09-12 16:36 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-11 20:34 Emacs inotify support? joakim
2009-09-11 21:28 ` Lennart Borgman
2009-09-11 22:54   ` Antoine Levitt
2009-09-11 23:00     ` Lennart Borgman
2009-09-12 13:32     ` Eli Zaretskii
2009-09-12 16:36       ` Antoine Levitt [this message]
2009-09-12 16:55         ` Eli Zaretskii
2009-09-12 17:26           ` Antoine Levitt
2009-09-12 19:45             ` Eli Zaretskii
2009-09-12 20:04               ` Antoine Levitt
2009-09-12 21:24               ` Giuseppe Scrivano
2009-09-13 16:39       ` Richard Stallman
2009-09-13 17:28         ` joakim
2009-09-13 19:42           ` Eli Zaretskii
2009-09-13 22:28             ` Lennart Borgman
2009-09-14  5:47             ` joakim
2009-09-14 18:08               ` Eli Zaretskii
2009-09-12 16:46     ` Richard Stallman
2009-09-13  2:27       ` Miles Bader
2009-09-13  9:33         ` David Kastrup
2009-09-12 16:46 ` Richard Stallman
2009-09-14  7:39   ` Paul R
2009-09-15  7:17     ` Richard Stallman
2009-09-17 15:12       ` Juri Linkov
2009-09-18  9:49         ` Richard Stallman
2009-09-18 12:10           ` David Kastrup
2009-09-18 17:14             ` Stefan Monnier
2009-09-18 18:38               ` joakim
2009-09-21 21:45           ` Dired auto-revert (was: Emacs inotify support?) Juri Linkov
2009-09-21 22:29             ` Drew Adams
2009-09-23  9:05               ` Dired auto-revert Juri Linkov
2009-12-04  0:11                 ` Proced revert (Re: Dired auto-revert) Juri Linkov
2009-12-04  2:17                   ` Stefan Monnier
2009-12-04 22:21                   ` Roland Winkler
2009-12-04  0:09               ` Dired auto-revert Juri Linkov
2009-12-04  2:15                 ` Stefan Monnier

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6fa54e4e0909120936s24634600sf00a818aabd308ce@mail.gmail.com \
    --to=antoine.levitt@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=joakim@verona.se \
    --cc=lennart.borgman@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.