bug#53432: [PATCH] Avoid losing keyboard input when inotify is too busy [and 1 more messages]

[Eli Zaretskii <eliz@gnu.org>]

> From: Po Lu <luangruo@yahoo.com>
> Cc: Eli Zaretskii <eliz@gnu.org>,  Ian Jackson
>  <ijackson@chiark.greenend.org.uk>,  53432@debbugs.gnu.org
> Date: Sun, 23 Jan 2022 11:26:22 +0800
> 
> Dmitry Gutov <dgutov@yandex.ru> writes:
> 
> > Is it? There are only two references to auto-revert-use-notify in
> > autorevert.el, and neither changes that var.
> >
> > Also see:
> >
> > etc/NEWS.25
> > 1108:*** 'auto-revert-use-notify' is set to nil in
> > 'global-auto-revert-mode'.
> >
> > etc/NEWS.26
> > 1070:** 'auto-revert-use-notify' is set back to t in
> > 'global-auto-revert-mode'.
> >
> > The latter coming with commit 484967796755051c4045cdcc26b0d3d129cc72ad.
> >
> > (Which was non-trivial to figure out because vc-annotate doesn't help
> > with NEWS files because of rotation.)
> 
> Hmm, maybe we should revert that commit, since file notifications are
> definitely not scalable enough to support such functionality.
> 
> Eli?

The nil setting was due to kqueue specific problem.  Michael fixed
that particular problem and therefore reverted the nil setting.

However, my opinion is still the same: file-notifications are not
scalable, so people who use and abuse them globally do that to their
own cost.  Not sure if it's worth forcing the notifications off,
though.  Perhaps we should have a PROBLEMS entry about that.