From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Michael Albinus Newsgroups: gmane.emacs.bugs Subject: bug#53432: [PATCH] Avoid losing keyboard input when inotify is too busy [and 1 more messages] Date: Mon, 24 Jan 2022 18:12:12 +0100 Message-ID: <877daprrbn.fsf@gmx.de> References: <25067.17249.604070.872185@chiark.greenend.org.uk> <838rv8nua8.fsf@gnu.org> <87r190wqo1.fsf@yahoo.com> <25068.23625.512978.147194@chiark.greenend.org.uk> <87a6fntgfh.fsf@yahoo.com> <25069.23134.887206.241281@chiark.greenend.org.uk> <877daqtnkw.fsf@gmx.de> <25069.40682.688423.883151@chiark.greenend.org.uk> <87lez5ry92.fsf@gmx.de> <83k0epji6b.fsf@gnu.org> <87h79trvt6.fsf@gmx.de> <83fspdjcu3.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="6643"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: luangruo@yahoo.com, 53432@debbugs.gnu.org, ijackson@chiark.greenend.org.uk To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Jan 24 18:18:53 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nC2zU-0001aO-16 for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 24 Jan 2022 18:18:52 +0100 Original-Received: from localhost ([::1]:34762 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nC2zS-0008Rj-Ud for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 24 Jan 2022 12:18:50 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:54052) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nC2tq-00072x-Ip for bug-gnu-emacs@gnu.org; Mon, 24 Jan 2022 12:13:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:52655) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nC2tq-0006zZ-7E for bug-gnu-emacs@gnu.org; Mon, 24 Jan 2022 12:13:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nC2tq-0003Y0-1I for bug-gnu-emacs@gnu.org; Mon, 24 Jan 2022 12:13:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Michael Albinus Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 24 Jan 2022 17:13:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 53432 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 53432-submit@debbugs.gnu.org id=B53432.164304434313580 (code B ref 53432); Mon, 24 Jan 2022 17:13:01 +0000 Original-Received: (at 53432) by debbugs.gnu.org; 24 Jan 2022 17:12:23 +0000 Original-Received: from localhost ([127.0.0.1]:45557 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nC2tD-0003Wy-EL for submit@debbugs.gnu.org; Mon, 24 Jan 2022 12:12:23 -0500 Original-Received: from mout.gmx.net ([212.227.17.20]:38395) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nC2tC-0003Wk-GP for 53432@debbugs.gnu.org; Mon, 24 Jan 2022 12:12:23 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1643044334; bh=HdKfCqkJXXPVz5y6hxyPghkPF2RyY8bPzi/dFrMfuPc=; h=X-UI-Sender-Class:From:To:Cc:Subject:References:Date:In-Reply-To; b=S6WhDNMsPBBqoMlo1legmsTXZvMiZBixpwRv8Ualw0hkzhaq0Mtl89+tWFdxtPtRo Gmf+XJqptBquebCyalrkZo/rqQwOjoeW8yDxznB+DDrKzqiFTrFCyjYOmqo4Tns2ZE za5O25Eew3udljXUOyaDzlmj2WK7Wcbt1hdMeFGo= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Original-Received: from gandalf.gmx.de ([79.140.118.216]) by mail.gmx.net (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MXp9Y-1mmgMr3ILs-00YDH7; Mon, 24 Jan 2022 18:12:13 +0100 In-Reply-To: <83fspdjcu3.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 24 Jan 2022 18:52:20 +0200") X-Provags-ID: V03:K1:HVu+CFFD8MAjR0cWQoK9gEvJ1TDnoMjHi7ExL+L9yki0oUBTyQL bknnKHHCWXaFztLycHDsCs07G5UY6TN9YFK4IdSayDOTNKSqyQHCTWDzzdYNEkMTm0QNf9p aqrCgm8F8mP4e+kwEf34oKN3hG1ZuwYlFxj6zg0V5kwTR4L0F88ufUu1FgGsevFKBTUoKac XLqD2i3bc/1LgNyYAkoIQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:Q7IV3/DepSg=:c/bUkn8zhXdnzlGQUEDeqr XBEF77A09y05NTHcWoa+G5H19xc9mid318H56/3vyfGuUadjoJPiw/JThJUMDwegbQZdyL3O6 VOMW2L3CK5HtzvF/Cu2hdKJBNdf2oVWwDAK8FeoCkn4Z8MAFiUr/kbIfIuw7nHcSW9UQiofuV M4MUuZ7RbWStOEUULcS9n1pJOEpI8+2t2bXjSvYJXJZEHdWWJX0eqymJqYvFahYcOrw7LvTsm QanTAI2ntn5P8hFmuvLHgfP+gsoF9IxrnhqYkwYh7DzZUCb5QaqS7c05Lg+mRZuDmBBXxzS0G l0WIGe3rsBXehu0gHgvJYw/Nbk2hMsgDhOuk5flUE9DC50wuNOVeKdA2SNsKPJPyl64kridov Qeya6/g2RIRDE5SqTS+UR2sgnY/XRFwrcJswYqTpqWucbJcH2Uq2iXlSOSzzfRRWXXoIVSQVe xfbapXDrruFw6frYb4DlKXkYDbDVU2VvjqLI5CgLx/RWMAn1gky84GVr/h8oWSJGEBeL3cbrr 4oJq/w7M9wewYhgfXcqS0OB/7lUXSArruF5h+mL1Oh/afcqYDBTR5AHiNmvbNgupNEiDK0LWg 0OxgbopIcoGgTrG7MauDu26PR2gO9idJHPWqwKTs0xqj+s2Mu6n5a3wTNYRrL6WDfo0WYjg+M IBZY3tACQ5p5spNSBWcr7nT97vUQO1xxVwUrsr+PGWlg8t5UWv/3SGTuL0CxND0wm/LZXkVKy 9N0Syqkm47DT2cmPnzeDvS5LPf+ji1CAx+uUhiv3iB8BKBQvg80l3cOalV3mjO3lqglMFl8b X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:225079 Archived-At: Eli Zaretskii writes: Hi Eli, >> > But the disadvantage is that we will immediately be facing a problem >> > of priority in handling input from more than one source. >> >> "Key strokes first!" :-) > > But it isn't only the key strokes, it's also all the events sent to us > by the window-system. Now tell me why, say, an expose event should be > more important than a file-notification event, and not the other way > around? After all, Emacs is still a text editor, isn't it? Key strokes and mouse events are the most important events, I believe. As rule of thumb, I would discriminate all events, which can aarive as burst, and which are already known to be lost sometimes. D-Bus and file notification events. If we classify other events into this category - no problem. >> An alternative approach could be to restrict how many burst events are >> put into the beyboard buffer. Let's say that D-Bus and file notificatio= n >> events are allowed to fill that buffer until (KBD_BUFFER_SIZE - 512) >> events (arbitrary number). This would let place for key strokes, mouse >> events and alike. > > That's what Po Lu was suggesting, AFAIU: limit the number of queued > file-notification events to not more than some threshold. Yep. And Ian is also on the same way, AFAIU. Best regards, Michael.