all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Tassilo Horn <tsdh@gnu.org>
Cc: 21435@debbugs.gnu.org
Subject: bug#21435: 25.0.50; file-notify has problems after renames
Date: Wed, 09 Sep 2015 20:15:09 +0200	[thread overview]
Message-ID: <877fnzv4r6.fsf@gmx.de> (raw)
In-Reply-To: <87si6og17z.fsf@gnu.org> (Tassilo Horn's message of "Tue, 08 Sep 2015 21:28:16 +0200")

Tassilo Horn <tsdh@gnu.org> writes:

>> But then Tassilo's "renames always seem to be reported twice" is
>> inaccurate: this should only happen when a file is moved to another
>> directory.
>
> See my other mail: the test if the source/target are different were done
> by testing if the descriptors are not `eq' but since inotify descriptors
> are conses, that test returned nil even though they were structurally
> equal.

Thanks for fixing this. I always had in mind that
`file-notify--descriptor' returns the same object, and maybe it did even
so in the past, but now it composes the cons itself. So we must test for
`equal', indeed.

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

And starting with inotify is also good because this is the library used
on hydra. We do not want to make Glenn sad because of failed tests.

>>> PPS: Forgive me slow progress; I'm still suffering from health
>>> problems.
>>
>> Wish you to recover quickly.
>
> Ditto!

Won't happen, unfortunately. It still takes months.

> Bye,
> Tassilo

Best regards, Michael.





  reply	other threads:[~2015-09-09 18:15 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-08  8:47 bug#21435: 25.0.50; file-notify has problems after renames Tassilo Horn
2015-09-08 16:03 ` Eli Zaretskii
2015-09-08 18:04   ` Michael Albinus
2015-09-08 18:21     ` Eli Zaretskii
2015-09-08 19:28       ` Tassilo Horn
2015-09-09 18:15         ` Michael Albinus [this message]
2015-09-09 19:01           ` Tassilo Horn
2015-09-09 20:23             ` Tassilo Horn
2015-09-10 11:23               ` Michael Albinus
2015-09-10 15:31                 ` Tassilo Horn
2015-09-10 17:50                   ` Michael Albinus
2015-09-10 19:22                     ` Tassilo Horn
2015-09-11  9:53                       ` Michael Albinus
2015-09-11 12:17                         ` Tassilo Horn
2015-09-11 12:32                           ` Eli Zaretskii
2015-09-12  8:44                           ` Michael Albinus
2015-09-11  9:45                     ` Michael Albinus
2015-09-11 12:11                       ` Tassilo Horn
2015-09-09 18:41       ` Michael Albinus
2015-09-09 19:21         ` Eli Zaretskii
2015-09-10 11:09           ` Michael Albinus
2015-09-10 15:45             ` Eli Zaretskii
2015-09-10 17:37               ` Michael Albinus
2015-09-10 18:03                 ` Eli Zaretskii
2015-09-10 18:20                   ` Michael Albinus
2015-09-10 18:55                     ` Eli Zaretskii
2015-09-11 12:51                       ` Michael Albinus
2015-09-08 19:05   ` Tassilo Horn
2015-09-08 19:19     ` Eli Zaretskii
2015-09-08 19:47       ` Tassilo Horn
2015-09-09  2:39         ` Eli Zaretskii
2015-09-09  6:13           ` Tassilo Horn
2015-09-20 17:26 ` Michael Albinus
2015-09-20 19:36   ` Eli Zaretskii
2015-09-21  6:25     ` Michael Albinus
2015-09-21  7:54       ` Eli Zaretskii
2015-09-21 10:13         ` Michael Albinus
2015-09-21 10:14           ` Eli Zaretskii
2015-09-21 13:11             ` Michael Albinus
2015-09-21 13:31               ` Eli Zaretskii
2015-09-21 13:38                 ` Michael Albinus

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=877fnzv4r6.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=21435@debbugs.gnu.org \
    --cc=tsdh@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.