GNU bug report logs - #21435
25.0.50; file-notify has problems after renames

Previous Next

Full log

Message #41 received at 21435 <at> debbugs.gnu.org (full text, mbox):

From: Tassilo Horn <tsdh <at> gnu.org>
To: Michael Albinus <michael.albinus <at> gmx.de>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 21435 <at> debbugs.gnu.org
Subject: Re: bug#21435: 25.0.50; file-notify has problems after renames
Date: Wed, 09 Sep 2015 21:01:18 +0200

Michael Albinus <michael.albinus <at> gmx.de> writes:

>>>> PS: Tassilo, you write great test cases. Do you want to contribute
>>>> to test/automated/file-notify-tests.el?
>>
>> Yes, but right now I can't because all these corner cases like the ones
>> from my last two reports are largely undocumented so I don't know what
>> to assert.  I myself don't have a strong opinion on the behavior of
>> file-notify as long as it's consistent across the different
>> `file-notify--library' possibilities (at least mostly, e.g., I can live
>> with created/deleted events in place of renamed in case the backend
>> doesn't support this) and the documentation is a bit more definite.
>
> Even the straigt forward cases are not covered well in
> file-notify-tests.el.  There is a test whether events arrive, but the
> nature of the events is not asserted.
>
> You could try with what you expect, at least for inotify, and Eli and
> I could check then for the gfilenotify and w32notify cases. If we have
> the same results, fine; if we have different results it would be a
> good chance for us to harmonize.

That's right.  I'll try adding some tests whenever I find some time.

Bye,
Tassilo

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.