From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Newsgroups: gmane.emacs.devel Subject: Re: GNU Emacs raison d'etre Date: Wed, 20 May 2020 21:53:36 +0200 Message-ID: <20200520195336.GA25403@tuxteam.de> References: <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> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="k1lZvvs/B4yU6o8G" Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="33191"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/1.5.21 (2010-09-15) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed May 20 21:54:30 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 1jbUnN-0008Wy-W3 for ged-emacs-devel@m.gmane-mx.org; Wed, 20 May 2020 21:54:29 +0200 Original-Received: from localhost ([::1]:44628 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jbUnN-0005Gi-0f for ged-emacs-devel@m.gmane-mx.org; Wed, 20 May 2020 15:54:29 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39754) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jbUmi-0004Qu-RU for emacs-devel@gnu.org; Wed, 20 May 2020 15:53:48 -0400 Original-Received: from mail.tuxteam.de ([5.199.139.25]:38018) by eggs.gnu.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.90_1) (envelope-from ) id 1jbUmh-0006E6-CG for emacs-devel@gnu.org; Wed, 20 May 2020 15:53:48 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tuxteam.de; s=mail; h=From:In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:To:Date; bh=Jd2hDxzSONqE3koks9obXFESjrqqExEwim93GoRAqU0=; b=VWOnMT5FjJ7H4GFb9KlgxhVjRIEmLUPAIL/QskGGo3SurnIcKUnnVAFDM/sDpuaXSZSdMBOdJo3l5NnIaz5XI17XK4lmh1PGq24AVCelwSabwX61F/rtLQMt5tOmmaXACgNuhE/C9GMJdrveHd/9+BlrsF6gJZ2r+2ame2UbPzm+6rnzhEs5EHWccDC5gfEfntKJjO272Xx4AkYYhGTwSM0rYtrqagoZILjBybWp9ht4osqzhSqaDz/3qKIQF2WIC0Ur65Y9/iM/BLp9njUfNyOetWceIXKi0qJEzqfFyHOpNMsu8AHozO+Qls6ptOaVG7VliPL/ccTgdb3CJsmxwA==; Original-Received: from tomas by mail.tuxteam.de with local (Exim 4.80) (envelope-from ) id 1jbUmW-0007LK-L7 for emacs-devel@gnu.org; Wed, 20 May 2020 21:53:36 +0200 Content-Disposition: inline In-Reply-To: <0015ade0-d4f9-6ccc-692c-222871251c51@yandex.ru> Received-SPF: pass client-ip=5.199.139.25; envelope-from=tomas@tuxteam.de; helo=mail.tuxteam.de X-detected-operating-system: by eggs.gnu.org: First seen = 2020/05/20 15:53:37 X-ACL-Warn: Detected OS = Linux 3.1-3.10 [fuzzy] X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN X-Spam_action: no action 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:251106 Archived-At: --k1lZvvs/B4yU6o8G Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 20, 2020 at 10:22:53PM +0300, Dmitry Gutov wrote: > On 20.05.2020 21:56, Eli Zaretskii wrote: > >To clarify: set-message-function is not supposed to affect all the > >ways we have to show something in the echo area, it is only supposed > >to affect calls to 'message', because that's how messages to the user > >are printed. > > > >eval-last-sexp uses prin1 to display the result, so it is not > >affected, as intended. >=20 > But aren't all echo area displays targeted at the user anyway? >=20 > I'm not saying the current behavior is necessarily "broken", but > perhaps we could enhance it further. Sorry, I don't quite understand. You are proposing that message-fun should not only take over messages proper but also the repl's print? Because (message "foo") displays foo twice (well once it's foo, as a side effect, then it's "foo", as the repl's "print" part, as the result of the S-expression's evaluation. FWIW, I'd expect setting set-message-function (strange name for a var, BTW) to just take over the side effect, not the repl's "print". But that's just one data point. Cheers -- t --k1lZvvs/B4yU6o8G Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAl7FisAACgkQBcgs9XrR2ka6ogCdGe5gIop6F3qIY5qrBAd8cotc N6cAn2tuEObRLniqAY2R2ECUvKatx+4a =zGW9 -----END PGP SIGNATURE----- --k1lZvvs/B4yU6o8G--