From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#40774: Error messages shouldn't be hidden when the user is idle Date: Tue, 14 Dec 2021 15:19:00 +0200 Message-ID: <83ee6fl3y3.fsf@gnu.org> References: <-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> <86bl1uyt8f.fsf@mail.linkov.net> <87r1aocf5p.fsf@gnus.org> <83czm7xozh.fsf@gnu.org> <86wnkerjgt.fsf@mail.linkov.net> <8335n2x3w5.fsf@gnu.org> <865yrtiqb6.fsf@mail.linkov.net> <83wnk9mwmx.fsf@gnu.org> <86v8ztfuga.fsf@mail.linkov.net> <831r2gmox3.fsf@gnu.org> <86sfuwnxtv.fsf@mail.linkov.net> <83o85kl2aq.fsf@gnu.org> <86ee6f4mqe.fsf@mail.linkov.net> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="37440"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 40774@debbugs.gnu.org, larsi@gnus.org, ndame@protonmail.com To: Juri Linkov Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Dec 14 14:30:51 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 1mx7tL-0009X8-2D for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 14 Dec 2021 14:30:51 +0100 Original-Received: from localhost ([::1]:54514 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mx7tJ-0007ZJ-P1 for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 14 Dec 2021 08:30:49 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:51186) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mx7is-0005eA-Sv for bug-gnu-emacs@gnu.org; Tue, 14 Dec 2021 08:20:04 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:46273) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mx7is-0001wl-Ja for bug-gnu-emacs@gnu.org; Tue, 14 Dec 2021 08:20:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1mx7is-0002Cs-Ex for bug-gnu-emacs@gnu.org; Tue, 14 Dec 2021 08:20:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 14 Dec 2021 13:20: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.16394879788445 (code B ref 40774); Tue, 14 Dec 2021 13:20:02 +0000 Original-Received: (at 40774) by debbugs.gnu.org; 14 Dec 2021 13:19:38 +0000 Original-Received: from localhost ([127.0.0.1]:57817 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mx7iT-0002C7-Lk for submit@debbugs.gnu.org; Tue, 14 Dec 2021 08:19:38 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:50346) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mx7iH-0002Bj-6D for 40774@debbugs.gnu.org; Tue, 14 Dec 2021 08:19:36 -0500 Original-Received: from [2001:470:142:3::e] (port=38014 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mx7iA-0001uN-4Q; Tue, 14 Dec 2021 08:19:18 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=qMhHuCPsGK5pXVGfV4Ry5AHJXTx+YT8y7ebt3hUrHI0=; b=OEZz4JQGZ4rz xCNs5ForrMof199D5OR7jxMRlP659NNj0kBJYS0vIiG0TAsuO56WBWtrodLHIciiYVQxER1x2ii3/ iHPKgRTpPawUmcEaLgICxyuh1vPHZU9AJHBbwqk2RCpMYIwqN9M/wp6A+xK5LG6Ug47elVFEgTwvD vPRKAm7UgdzJxkq+NqmUWIO+dco4nm3PXtL+Cl2EIxoaMBIl586R1h9pZe+/eg6Tgp14kTz1riPpN 0atIpIT/RZzbwuGn7ovh3z/ixEA0ttGfKEojhJZeIq5Dgz69+hq5DD8ECIua/vZrnCETzMKioR5oJ B93+RPrGcFRbVEZIxHTpGA==; Original-Received: from [87.69.77.57] (port=4924 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mx7hv-00010P-Cc; Tue, 14 Dec 2021 08:19:06 -0500 In-Reply-To: <86ee6f4mqe.fsf@mail.linkov.net> (message from Juri Linkov on Tue, 14 Dec 2021 10:35:13 +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:222368 Archived-At: > From: Juri Linkov > Cc: larsi@gnus.org, 40774@debbugs.gnu.org, ndame@protonmail.com > Date: Tue, 14 Dec 2021 10:35:13 +0200 > > > So there will be some effect of this reordering, if some > > clear-message-function does something that you say it shouldn't. > > Of course, when authors decide to shoot themselves in the foot, > we can't prevent this. They might say we shoot them in their foot, by changing the order. > > This whole discussion started from a request to be able to accumulate > > messages in the echo-area so that the user who is away could see them > > all when he/she comes back from whatever took him/her away. There > > could be quite a lot of messages accumulated during that period, and > > the request was to leave them all on display. For which you proposed > > to use clear-message-function in a way that doesn't actually clear > > them. > > > > Is the above an accurate description and summary of what is being > > proposed here? If so, is it now clear what kind of job I think > > display of echo-area messages was never designed to support? > > Thanks for explanation, now it's clear where is the misunderstanding. > > Actually, the patch for clear-message-function here is unrelated > to the feature that uses set-message-function to accumulate messages > and doesn't use clear-message-function. > > The feature here is intended for users who want to always leave > the last displayed message in the echo-area, and never clear it. > It will be possible even to do this conditionally. But if messages aren't cleared, they will accumulate, and then we get to the problems I described. So it is not "unrelated", really. In any case, if this feature is unrelated, why do you want to have it on the release branch?