From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.bugs Subject: bug#40774: Error messages shouldn't be hidden when the user is idle Date: Mon, 06 Dec 2021 06:49:33 +0100 Message-ID: <87tufmnuz6.fsf@gnus.org> 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> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="25561"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: 40774@debbugs.gnu.org, ndame@protonmail.com To: Juri Linkov Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Dec 06 06:50:16 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 1mu6tD-0006Tt-N4 for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 06 Dec 2021 06:50:15 +0100 Original-Received: from localhost ([::1]:53148 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mu6tC-0006es-At for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 06 Dec 2021 00:50:14 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:41322) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mu6t0-0006eU-GF for bug-gnu-emacs@gnu.org; Mon, 06 Dec 2021 00:50:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:48769) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mu6t0-0007DU-8T for bug-gnu-emacs@gnu.org; Mon, 06 Dec 2021 00:50:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1mu6t0-0000Az-4r for bug-gnu-emacs@gnu.org; Mon, 06 Dec 2021 00:50:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Lars Ingebrigtsen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 06 Dec 2021 05:50: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.1638769788649 (code B ref 40774); Mon, 06 Dec 2021 05:50:02 +0000 Original-Received: (at 40774) by debbugs.gnu.org; 6 Dec 2021 05:49:48 +0000 Original-Received: from localhost ([127.0.0.1]:60315 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mu6sm-0000AP-3r for submit@debbugs.gnu.org; Mon, 06 Dec 2021 00:49:48 -0500 Original-Received: from quimby.gnus.org ([95.216.78.240]:60674) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mu6sl-0000AC-3Y for 40774@debbugs.gnu.org; Mon, 06 Dec 2021 00:49:47 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date: References:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=LR0AM16YcBRfXDxMnTDZ87phKeQNGxNEymV09ip5CG8=; b=egRwpVyQ5+BgOnu9A8DZByRRzR GXobrodBY5TFWXriy0Mn9+7aqcChr5twfdK6AGs3LSXIyajat6vhkwhpAlFOTcSeYIPkxcj9bhxD9 9fVRYfStKfUFmX5qcBOJLDr2A+ee3tcB15Zic4+0SKqTijdb1SqjuEwr4ZHPfjXrhUYc=; Original-Received: from [84.212.220.105] (helo=xo) by quimby.gnus.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mu6sY-0002Z0-44; Mon, 06 Dec 2021 06:49:36 +0100 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAABGdBTUEAALGPC/xhBQAAACBj SFJNAAB6JgAAgIQAAPoAAACA6AAAdTAAAOpgAAA6mAAAF3CculE8AAAAD1BMVEUrJi11nLmnL0aw Gi////+K8Yg8AAAAAWJLR0QEj2jZUQAAAAd0SU1FB+UMBgUtHrYoNysAAAG1SURBVDjLjZMJbsQg DEVZLoDpBQhcIAP3v1v//yZLpUqtpZk4ed4NIZoVKxFSi4VSzEK1YCEkI4oWD4MARJMSgiWrJVYC 8FLi/g4vAjesCMsQCCqQ7lC1lECbWByYHR4aBXgWxgoRCEKbBlCDqtpSwiNr+XOsFvLR6amvkHNr c/ANIK8tt4nMYn70n2DcOlwyMowHwOnMDqbyTw/FLPydDmDaHHQY9yFQJ5pe/HLG+k5e1+zTmOW0 rxtMjAyPj8Ah0MeuyvSp6r/gv+ULwKKVBB0zfedQlN4d5DUTVbZgd7tcB2MkH9VTioNJb+2o84Xu AOHKTAArTevQPu+hB9Y4CaJAGtf+3gLitbS946sSnLh6TSR4vnGBXaNAS6joS82Wa4mIVbKl9ald 4F504xCP0ad2Ex9AK6QznqDJw6ytt7CB70mdD9SAzHltUDVRdJh5+Hof20Nb+0QBP5cEpqOhWaFz KsM3aOOI3VNsUFUWljDRBRzCBmNohbAbHgmq+kDu9RHgfCYud5RHYy1NgAs9aG7sYKVUHXDAiq/7 piM378sXTdcRt/i9qD8k9dbSbyDy9v8jwDePd3DtvJKNeAAAACV0RVh0ZGF0ZTpjcmVhdGUAMjAy MS0xMi0wNlQwNTo0NTozMCswMDowMJymWlcAAAAldEVYdGRhdGU6bW9kaWZ5ADIwMjEtMTItMDZU MDU6NDU6MzArMDA6MDDt++LrAAAAAElFTkSuQmCC X-Now-Playing: Talking Heads's _Remain In Light (vinyl)_: "Born Under Punches (The Heat Goes On)" In-Reply-To: <86czmakaem.fsf@mail.linkov.net> (Juri Linkov's message of "Sun, 05 Dec 2021 23:29:53 +0200") 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:221720 Archived-At: Juri Linkov writes: > Maybe, add a new function 'clear-message-function-2', > then in the next release delete 'clear-message-function', > and after the next release rename 'clear-message-function-2' to > 'clear-message-function'. Let's call it `new-message-function', and then in the next release, `new-message-function-final'? I think that's more up to industry standard specs. > 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? -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no