all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Barry Margolin <barmar@alum.mit.edu>
To: help-gnu-emacs@gnu.org
Subject: Re: why 4 inotfy events when saving a file?
Date: Sun, 10 Mar 2013 20:59:22 -0400	[thread overview]
Message-ID: <barmar-10F9B9.20592210032013@news.eternal-september.org> (raw)
In-Reply-To: mailman.21821.1362951956.855.help-gnu-emacs@gnu.org

In article <mailman.21821.1362951956.855.help-gnu-emacs@gnu.org>,
 Gregor Zattler <telegraph@gmx.net> wrote:

> Dear Emacs users and developers,
> 
> saving a file from Emacs gives 4 inotify events:
> 
> how to reproduce:
> 
>    on first terminal do:
>       emacs-snapshot -nw -Q /tmp/inotify.test
>       modify file
>    
>    
>    on second terminal do
>       inotifywait -m  -q --format '%e %w%f' /tmp/inotify.test
>    
>    
>    on first terminal do 
>       ^x^s (safe buffer)
>    
>    result on second terminal is:
>       MODIFY /tmp/inotify.test
>       OPEN /tmp/inotify.test
>       MODIFY /tmp/inotify.test
>       CLOSE_WRITE,CLOSE /tmp/inotify.test
> 
> 
> why are there so many events?

To save the backup file. First it renames inotify.test to 
inotify.test.~<version>~, then it writes the buffer to a new 
inotify.test file.

-- 
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***


       reply	other threads:[~2013-03-11  0:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.21821.1362951956.855.help-gnu-emacs@gnu.org>
2013-03-11  0:59 ` Barry Margolin [this message]
2013-03-10 21:44 why 4 inotfy events when saving a file? Gregor Zattler
2013-03-10 22:09 ` Eli Zaretskii
2013-03-11 23:14   ` Gregor Zattler
2013-03-12  3:07     ` William Gardella
     [not found]   ` <mailman.21890.1363043748.855.help-gnu-emacs@gnu.org>
2013-03-12  2:21     ` B. T. Raven

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=barmar-10F9B9.20592210032013@news.eternal-september.org \
    --to=barmar@alum.mit.edu \
    --cc=help-gnu-emacs@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 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.