bug#22454: 24.5; win32 file-notify, input events caused by updates to other (non-watched) files

[Noam Postavsky]

On Sun, Jan 24, 2016 at 10:20 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> When you ask to watch a file, file-notify-add-watch actually watches
> the entire directory of that file

Oh.  In this case I thought it was only files beneath .git/ that were
being changed (while we we are watching a file in the working copy),
but (trace-function 'file-notify-callback) tells me that Emacs is
receiving events about the .git/ directory.

>> This does not occur on GNU/Linux systems.
>
> Did those systems use inotify or the gfilenotify back-end?

I think gfilenotify, but I only have access to a Windows box for the
next couple of weeks, so I'm not 100% sure.

> I don't think it's either a bug or a limitation.  File notifications
> generate input events, so the current implementation of sit-for has a
> good reason to stop waiting.  The way the input events are generated
> differ between different back-ends, so perhaps the difference in
> behavior you see is due to that, but in general I think the fact that
> you didn't see that on GNU/Linux is more luck than anything else.

Ok, sounds like there is nothing to fix on the Emacs side, so I'm closing this.