From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: tomas@tuxteam.de Newsgroups: gmane.emacs.devel Subject: Re: GNU Emacs raison d'etre Date: Thu, 21 May 2020 09:43:54 +0200 Message-ID: <20200521074354.GB26656@tuxteam.de> References: <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> <20200520195336.GA25403@tuxteam.de> <3d02a63d-5f84-1c94-43de-e077e999ead6@yandex.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mojUlQ0s9EVzWg2t" Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="88180"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/1.5.21 (2010-09-15) Cc: emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu May 21 09:44:28 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 1jbfsR-000MmF-A7 for ged-emacs-devel@m.gmane-mx.org; Thu, 21 May 2020 09:44:27 +0200 Original-Received: from localhost ([::1]:37280 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jbfsQ-0006b5-Bn for ged-emacs-devel@m.gmane-mx.org; Thu, 21 May 2020 03:44:26 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47716) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jbfry-0006CQ-PA for emacs-devel@gnu.org; Thu, 21 May 2020 03:43:58 -0400 Original-Received: from mail.tuxteam.de ([5.199.139.25]:39485) by eggs.gnu.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.90_1) (envelope-from ) id 1jbfrx-000623-8G for emacs-devel@gnu.org; Thu, 21 May 2020 03:43:58 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tuxteam.de; s=mail; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=2oCa5tf+jX5aafsI6ndSKQSFF9XGU++yijBLTmhRiLM=; b=O2GTM414VcLlOVn7P/NCsKHMJNvjxPeuqXNBg2ygkZ3+cLG68hG5zmqGts2GQhwoAMAdaUfcTA6oIzPcAMueKA+/VK0NYdUGsJRyjJJ55dF9vIdQ+R9J7GYnV698cIv7bkknq5t25drzUya7EtDlWocA3aGyzYiQQvtlKoafh/UMxGotMhyptRB7HVtoeZhqsANAavfuUI0AOTS1pH5lNjI3YzDg1QJsZBHhllLcfwIvBgW43HjCj8SRwZTnDeJ17N/Rg/9QSKyW7vui4G4g2vJqcA41fadbMwXZyN5VnVoNPWbvb7xyHYZvbweUWzkKjiLPr5xzLFRDKHocmUFH9A==; Original-Received: from tomas by mail.tuxteam.de with local (Exim 4.80) (envelope-from ) id 1jbfrv-0007K6-0K; Thu, 21 May 2020 09:43:55 +0200 Content-Disposition: inline In-Reply-To: <3d02a63d-5f84-1c94-43de-e077e999ead6@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/21 03:43:55 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:251152 Archived-At: --mojUlQ0s9EVzWg2t Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 21, 2020 at 12:22:04AM +0300, Dmitry Gutov wrote: > On 20.05.2020 22:53, tomas@tuxteam.de wrote: > >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? >=20 > Yes, why not? I think, at the end it's a matter of taste/expectations, so don't attach too much weight to mine. > >Because (message "foo") displays foo twice [...] > When it is evaluated in the REPL, yes. Because you're seeing both > the result of 'message' itself, as well as the result of > eval-expression. Exactly. And I'd expect `set-message-function' to only touch the `(message)' part -- but see above. > Do you have an example of set-message-function where it would be a bad id= ea? Hm. I don't quite understand your question: I suspect that we're talking past each other, but I can't yet grasp how. It's not "examples" I'd looking for. It's just that in my head, the "print" of REPL and the "message" are two different things, and should be controlled by different knobs. But, as I said above, it's something rather subjective. Cheers -- t --mojUlQ0s9EVzWg2t Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAl7GMToACgkQBcgs9XrR2kYzVQCfQUR4XviVME12jy0M0XpeLNPC a9YAn0Q9urt9InbdRD2mjAQZ6mzlfwjy =67AL -----END PGP SIGNATURE----- --mojUlQ0s9EVzWg2t--