Subject: Re: bug#21435: 25.0.50; file-notify has problems after renames

From: Michael Albinus <[email-masked]>
Date: Mon, 21 Sep 2015 12:13:23 +0200

Eli Zaretskii <[email-masked]> writes:

Hi Eli,

>> However, as said I have extended the test case a little bit. There are
>> now set-file-times and set-file-modes calls, which shall result in
>> attribute-changed events. And those events shall be suppressed, because
>> we start file notifications with (file-notify-add-watch ... '(change) ...)
>> 
>> How does w32notify report attribute changes?
>
> As documented: it returns 'modified'.

Hmm. So it does not distinguish between "contents changed" and
"attribute changed", as the other backends do.

What a pity! We must document it then.

Best regards, Michael.