[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#21435: 25.0.50; file-notify has problems after renames
From: |
Michael Albinus |
Subject: |
bug#21435: 25.0.50; file-notify has problems after renames |
Date: |
Mon, 21 Sep 2015 12:13:23 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) |
Eli Zaretskii <eliz@gnu.org> 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.
- bug#21435: 25.0.50; file-notify has problems after renames, (continued)
bug#21435: 25.0.50; file-notify has problems after renames, Michael Albinus, 2015/09/20
- bug#21435: 25.0.50; file-notify has problems after renames, Eli Zaretskii, 2015/09/20
- bug#21435: 25.0.50; file-notify has problems after renames, Michael Albinus, 2015/09/21
- bug#21435: 25.0.50; file-notify has problems after renames, Eli Zaretskii, 2015/09/21
- bug#21435: 25.0.50; file-notify has problems after renames,
Michael Albinus <=
- bug#21435: 25.0.50; file-notify has problems after renames, Eli Zaretskii, 2015/09/21
- bug#21435: 25.0.50; file-notify has problems after renames, Michael Albinus, 2015/09/21
- bug#21435: 25.0.50; file-notify has problems after renames, Eli Zaretskii, 2015/09/21
- bug#21435: 25.0.50; file-notify has problems after renames, Michael Albinus, 2015/09/21