From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.bugs Subject: bug#40774: Error messages shouldn't be hidden when the user is idle Date: Mon, 06 Dec 2021 11:31:44 +0200 Organization: LINKOV.NET Message-ID: <86bl1uyt8f.fsf@mail.linkov.net> References: <83blnje5ro.fsf@gnu.org> <838sine4si.fsf@gnu.org> <837dy7e3wr.fsf@gnu.org> <-ZmNQQ07JD7L0I5EpXolv4t1UhWBGc4SN0dkJml3cLbBjO6ucAMUzAqsI9Ca69xO_hzlMLfaLs6bY9vq8GAR24RUGu1LZqVoVkXhiJcFgtg=@protonmail.com> <835zdre31u.fsf@gnu.org> <87v9lpluez.fsf@mail.linkov.net> <874koxwi1t.fsf@gnus.org> <86pmqa51cz.fsf@mail.linkov.net> <87bl1uojxd.fsf@gnus.org> <86czmakaem.fsf@mail.linkov.net> <87tufmnuz6.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="12267"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (x86_64-pc-linux-gnu) Cc: 40774@debbugs.gnu.org, ndame@protonmail.com To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Dec 06 10:40:57 2021 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 1muAUT-0002vM-8H for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 06 Dec 2021 10:40:57 +0100 Original-Received: from localhost ([::1]:57774 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1muAUS-0002bA-7j for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 06 Dec 2021 04:40:56 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:58256) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1muATb-0001QY-2M for bug-gnu-emacs@gnu.org; Mon, 06 Dec 2021 04:40:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:49015) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1muATa-0008W4-Qt for bug-gnu-emacs@gnu.org; Mon, 06 Dec 2021 04:40:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1muATa-000697-He for bug-gnu-emacs@gnu.org; Mon, 06 Dec 2021 04:40:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Juri Linkov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 06 Dec 2021 09:40:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 40774 X-GNU-PR-Package: emacs Original-Received: via spool by 40774-submit@debbugs.gnu.org id=B40774.163878358623561 (code B ref 40774); Mon, 06 Dec 2021 09:40:02 +0000 Original-Received: (at 40774) by debbugs.gnu.org; 6 Dec 2021 09:39:46 +0000 Original-Received: from localhost ([127.0.0.1]:60554 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1muATK-00067x-F8 for submit@debbugs.gnu.org; Mon, 06 Dec 2021 04:39:46 -0500 Original-Received: from relay9-d.mail.gandi.net ([217.70.183.199]:35243) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1muATI-00067M-NU for 40774@debbugs.gnu.org; Mon, 06 Dec 2021 04:39:44 -0500 Original-Received: (Authenticated sender: juri@linkov.net) by relay9-d.mail.gandi.net (Postfix) with ESMTPSA id A7007FF810; Mon, 6 Dec 2021 09:39:36 +0000 (UTC) In-Reply-To: <87tufmnuz6.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 06 Dec 2021 06:49:33 +0100") 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:221734 Archived-At: >> But really it's not worth the trouble. I counted 60 incompatible >> Lisp changes in Emacs 28.1. And if we will make this change now, >> the authors will have enough time to adapt their code >> (though I can't find any use of this new variable anywhere). > > It's true that it's not likely to have been used a lot, so perhaps it's > an acceptable change in semantics. Perhaps try a search on Github and > see whether anybody's using it there? I can't find it on Github, and this is understandable - it's a new variable with quite limited usefulness. I hoped that even if someone used it, mentioning it in the Incompatible Lisp Changes of NEWS would be sufficient as in case of all other incompatible changes.