From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: GNU Emacs raison d'etre Date: Fri, 22 May 2020 10:28:10 +0300 Message-ID: <83zha0ig39.fsf@gnu.org> References: <5230692c-c665-a330-7a12-e59fa25d97dd@gmail.com> <83sgfybn22.fsf@gnu.org> <1701f0b1-a481-bb45-08b8-99da4a6139fc@gmx.at> <736c1336-58ea-dd1f-18ba-94f902e37f61@yandex.ru> <206d0959-8a6f-ebf9-0230-1cdb41a0c849@gmx.at> <79aa434b-6513-14ff-eb45-ece4ba30590b@yandex.ru> <83eere7jil.fsf@gnu.org> <834ksa7fgy.fsf@gnu.org> <0db86fd4-3add-7863-9102-849a9d270cc3@gmx.at> <83sgfu5vhs.fsf@gnu.org> <8fc4ea19-35ff-5c34-4a25-e1b47ee79e77@yandex.ru> <83pnay5udk.fsf@gnu.org> <83mu625tav.fsf@gnu.org> <0015ade0-d4f9-6ccc-692c-222871251c51@yandex.ru> <83imgq58dm.fsf@gnu.org> <57928502-aec4-4042-5ac8-d38a960c920b@yandex.ru> Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="107182"; mail-complaints-to="usenet@ciao.gmane.io" Cc: jean.christophe.helary@traduction-libre.org, rms@gnu.org, andreas.roehler@online.de, emacs-devel@gnu.org, kfogel@red-bean.com, rudalics@gmx.at, homeros.misasa@gmail.com, tkk@misasa.okayama-u.ac.jp, sorganov@gmail.com, monnier@iro.umontreal.ca, arthur.miller@live.com, drew.adams@oracle.com, stefankangas@gmail.com To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri May 22 09:28:56 2020 Return-path: Envelope-to: ged-emacs-devel@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 1jc26y-000RnH-Dt for ged-emacs-devel@m.gmane-mx.org; Fri, 22 May 2020 09:28:56 +0200 Original-Received: from localhost ([::1]:58438 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jc26x-0008PS-Gw for ged-emacs-devel@m.gmane-mx.org; Fri, 22 May 2020 03:28:55 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41570) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jc26W-0007u7-Av for emacs-devel@gnu.org; Fri, 22 May 2020 03:28:28 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:59263) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jc26P-00080E-D7; Fri, 22 May 2020 03:28:21 -0400 Original-Received: from [176.228.60.248] (port=3240 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jc26F-0002NE-2b; Fri, 22 May 2020 03:28:11 -0400 In-Reply-To: <57928502-aec4-4042-5ac8-d38a960c920b@yandex.ru> (message from Dmitry Gutov on Fri, 22 May 2020 01:19:54 +0300) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:251199 Archived-At: > Cc: jean.christophe.helary@traduction-libre.org, rms@gnu.org, > andreas.roehler@online.de, emacs-devel@gnu.org, kfogel@red-bean.com, > rudalics@gmx.at, homeros.misasa@gmail.com, tkk@misasa.okayama-u.ac.jp, > sorganov@gmail.com, monnier@iro.umontreal.ca, arthur.miller@live.com, > drew.adams@oracle.com, stefankangas@gmail.com > From: Dmitry Gutov > Date: Fri, 22 May 2020 01:19:54 +0300 > > >> I'm not saying the current behavior is necessarily "broken", but perhaps > >> we could enhance it further. > > The intent was to affect messages that are a "surprise" for the user. > > eval-last-sexp is invoked by the user, so no surprise here. > > But not all 'message' calls are a "surprise". One might even say that > the vast majority of them aren't. And yet, they obey set-message-function. We provided a possibility to customize this functionality out of principle, without investing too much research into the various ways this could be used in situations very different from those for which the code was written, which is display of a message when the minibuffer is active. It is possible that using this as a customization tool in other situations could also make sense, and that other sense would then suggest us that the feature should be extended to other means of displaying messages in the echo area. However, it sounds too early to consider those additional possibilities. I'd like first to collect real-life use experience with this feature in Emacs 27.