From: Dmitry Gutov <dgutov@yandex.ru>
To: Po Lu <luangruo@yahoo.com>
Cc: 53432@debbugs.gnu.org, Ian Jackson <ijackson@chiark.greenend.org.uk>
Subject: bug#53432: [PATCH] Avoid losing keyboard input when inotify is too busy [and 1 more messages]
Date: Sun, 23 Jan 2022 05:36:06 +0200 [thread overview]
Message-ID: <a27dc3d3-a3e8-988f-778b-195c659f7fad@yandex.ru> (raw)
In-Reply-To: <87fspfrv35.fsf@yahoo.com>
On 23.01.2022 05:26, Po Lu via Bug reports for GNU Emacs, the Swiss army
knife of text editors wrote:
> Hmm, maybe we should revert that commit, since file notifications are
> definitely not scalable enough to support such functionality.
VS Code et al. seem to disagree, though (*).
But it does sound like you want to discuss this issue with Michael, at
least.
(*) These pages might be of interest:
https://stackoverflow.com/questions/50901127/vsc-unable-to-watch-for-file-changes-in-this-large-workspace-weird
https://github.com/microsoft/vscode-docs/blob/vnext/release-notes/v1_62.md#file-watching-changes
next prev parent reply other threads:[~2022-01-23 3:36 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 23:36 bug#53432: [PATCH] Avoid losing keyboard input when inotify is too busy Ian Jackson
2022-01-22 0:38 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-22 19:34 ` bug#53432: [PATCH] Avoid losing keyboard input when inotify is too busy [and 1 more messages] Ian Jackson
2022-01-22 19:48 ` Eli Zaretskii
2022-01-23 2:37 ` Dmitry Gutov
2022-01-23 2:47 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-23 2:49 ` Dmitry Gutov
2022-01-23 2:53 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-23 3:23 ` Dmitry Gutov
2022-01-23 3:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-23 3:36 ` Dmitry Gutov [this message]
2022-01-23 3:48 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-23 4:07 ` Dmitry Gutov
2022-01-23 5:50 ` Eli Zaretskii
2022-01-23 16:34 ` Michael Albinus
2022-01-23 1:00 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-23 13:38 ` Ian Jackson
2022-01-23 16:37 ` Michael Albinus
2022-01-23 18:31 ` Ian Jackson
2022-01-24 0:42 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-24 14:42 ` Michael Albinus
2022-01-24 14:57 ` Eli Zaretskii
2022-01-24 15:35 ` Michael Albinus
2022-01-24 16:52 ` Eli Zaretskii
2022-01-24 17:12 ` Michael Albinus
2022-01-24 17:25 ` Eli Zaretskii
2022-01-24 15:45 ` Ian Jackson
2022-01-24 17:05 ` Michael Albinus
2022-01-24 18:59 ` Ian Jackson
2022-01-25 14:50 ` Michael Albinus
2022-01-24 0:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-22 6:45 ` bug#53432: [PATCH] Avoid losing keyboard input when inotify is too busy Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a27dc3d3-a3e8-988f-778b-195c659f7fad@yandex.ru \
--to=dgutov@yandex.ru \
--cc=53432@debbugs.gnu.org \
--cc=ijackson@chiark.greenend.org.uk \
--cc=luangruo@yahoo.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).