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: Wed, 15 Dec 2021 14:41:11 +0200 Message-ID: <83a6h2jb14.fsf@gnu.org> References: <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> <83ee6fl3y3.fsf@gnu.org> <86fsquucte.fsf@mail.linkov.net> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="584"; 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 Wed Dec 15 13:43:33 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 1mxTd7-000AW8-65 for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 15 Dec 2021 13:43:33 +0100 Original-Received: from localhost ([::1]:46018 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mxTd5-0004lC-A3 for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 15 Dec 2021 07:43:31 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:48730) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mxTbf-0004Dg-Ro for bug-gnu-emacs@gnu.org; Wed, 15 Dec 2021 07:42:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:48880) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mxTbe-0005kI-DY for bug-gnu-emacs@gnu.org; Wed, 15 Dec 2021 07:42:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1mxTbe-0006HI-Ax for bug-gnu-emacs@gnu.org; Wed, 15 Dec 2021 07:42: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: Wed, 15 Dec 2021 12:42: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.163957209924096 (code B ref 40774); Wed, 15 Dec 2021 12:42:02 +0000 Original-Received: (at 40774) by debbugs.gnu.org; 15 Dec 2021 12:41:39 +0000 Original-Received: from localhost ([127.0.0.1]:60426 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mxTbH-0006GZ-Cq for submit@debbugs.gnu.org; Wed, 15 Dec 2021 07:41:39 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:47868) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mxTbG-0006GN-3z for 40774@debbugs.gnu.org; Wed, 15 Dec 2021 07:41:39 -0500 Original-Received: from [2001:470:142:3::e] (port=46816 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 1mxTbA-0005b0-F6; Wed, 15 Dec 2021 07:41:32 -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=0yfdiakE0eKWtneWpsWA77hbAgPI+QcJDYCci5k7GyA=; b=BnSB6Q+cpIka HPgGwvcdkUmODFN8UQmwfWvHmkisQDgxocnZlKYulwR+Yx+hfE5Brr8Tq18brbenFIznAuee+dMKF fV6S7+OaA6fWLYSL220AYlUdUpaCOHusE7q0PEMYtl/tNE2dbmMx9oE3EKlk+ve2oOcbxgDxkCyOW rsHkQupA4n1YD/zLwial9tIxv8n4mNCsfKijpRDn6ZgX+N3hH1kEIVKGXUxkkscjGKcjIlewAUFTu wUlmiu1Puuk/P5vGR3e8yW0cEeGofXfVBYyfrk4l6dc623F4r3Y13D8TBAfzm1HVtNgXAfM5xkJmq 9CJzvsVCyjG+AcdhBeSWUw==; Original-Received: from [87.69.77.57] (port=3241 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 1mxTb8-0006F8-Hm; Wed, 15 Dec 2021 07:41:32 -0500 In-Reply-To: <86fsquucte.fsf@mail.linkov.net> (message from Juri Linkov on Tue, 14 Dec 2021 22:54: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:222416 Archived-At: > From: Juri Linkov > Cc: larsi@gnus.org, 40774@debbugs.gnu.org, ndame@protonmail.com > Date: Tue, 14 Dec 2021 22:54:53 +0200 > > >> > 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. > > When the message is not cleared, it will be displayed until another message > will replace it. This is unrelated to multi-message feature. OK, then I guess it was a mistake to discuss this under this particular bug report. > > In any case, if this feature is unrelated, why do you want to have it > > on the release branch? > > This is another misunderstanding. I didn't intend to have this > on the release branch. But since you mentioned it, why not? Because we are done experimenting on the release branch. Only bugfixes should be installed there.