why 4 inotfy events when saving a file?

why 4 inotfy events when saving a file?

[Gregor Zattler]

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?



This is with 
GNU Emacs 24.3.50.1 (i486-pc-linux-gnu, GTK+ Version 3.4.2) of
2013-03-04 on dex, modified by Debian



Thanx for your attention, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-

Re: why 4 inotfy events when saving a file?

[Eli Zaretskii]

> Date: Sun, 10 Mar 2013 22:44:42 +0100
> From: Gregor Zattler <telegraph@gmx.net>
> 
> 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?

Because that's what Emacs does when it saves the file, first to the
old version, then to the new.  Take a look at the implementation of
write-region, which is the primitive used by save-buffer to write the
buffer to its file, you will see all those operations there.

Re: why 4 inotfy events when saving a file?

[Barry Margolin]

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 ***

Re: why 4 inotfy events when saving a file?

[Gregor Zattler]

Hi Eli, Emacs users and developers,
* Eli Zaretskii <eliz@gnu.org> [11. Mar. 2013]:
>> Date: Sun, 10 Mar 2013 22:44:42 +0100
>> From: Gregor Zattler <telegraph@gmx.net>
>> 
>> saving a file from Emacs gives 4 inotify events:
[...]
>> why are there so many events?
> 
> Because that's what Emacs does when it saves the file, first to the
> old version, then to the new.  Take a look at the implementation of
> write-region, which is the primitive used by save-buffer to write the
> buffer to its file, you will see all those operations there.

Thanks (also to Barry Margolin) for the explanation.  I now
search for a after-file-save-hook.  But I didn't find it.  Is
there some such thing?


Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-

Re: why 4 inotfy events when saving a file?

[B. T. Raven]

> Hi Eli, Emacs users and developers,
> * Eli Zaretskii <eliz@gnu.org> [11. Mar. 2013]:
>>> Date: Sun, 10 Mar 2013 22:44:42 +0100
>>> From: Gregor Zattler <telegraph@gmx.net>
>>>
>>> saving a file from Emacs gives 4 inotify events:
> [...]
>>> why are there so many events?
>>
>> Because that's what Emacs does when it saves the file, first to the
>> old version, then to the new.  Take a look at the implementation of
>> write-region, which is the primitive used by save-buffer to write the
>> buffer to its file, you will see all those operations there.
> 
> Thanks (also to Barry Margolin) for the explanation.  I now
> search for a after-file-save-hook.  But I didn't find it.  Is
> there some such thing?

C-h v after TAB shows:

after-save-hook is a variable defined in `files.el'.
Its value is nil

  This variable is potentially risky when used as a file local variable.

Documentation:
Normal hook that is run after a buffer is saved to its file.

You can customize this variable.

Ed

> 
> 
> Ciao, Gregor
> 

Re: why 4 inotfy events when saving a file?

[William Gardella]

Hi Gregor,

Gregor Zattler <telegraph-hi6Y0CQ0nG0@public.gmane.org> writes:

> Thanks (also to Barry Margolin) for the explanation.  I now
> search for a after-file-save-hook.  But I didn't find it.  Is
> there some such thing?
>
>
> Ciao, Gregor

There is, in, fact, an `after-save-hook'.  :) Please see also (info
"(elisp) Saving Buffers").

-- 
Regards,
WGG