From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: evaluating numbers Date: Fri, 08 Nov 2019 15:49:04 +0200 Message-ID: <835zjucwbz.fsf@gnu.org> References: <875zjw2emg.fsf@gmx.net> <618B38D9-CD34-4200-8CA1-1A6B0922A83A@traduction-libre.org> <871ruk2d3f.fsf@gmx.net> <3C929D7B-1C10-4713-9EDA-55C80FC36AD8@traduction-libre.org> <835zjvg385.fsf@gnu.org> <83sgmyd6rw.fsf@gnu.org> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="190655"; mail-complaints-to="usenet@blaine.gmane.org" Cc: emacs-devel@gnu.org To: Jean-Christophe Helary Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Nov 08 14:49:39 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iT4du-000nT1-Kx for ged-emacs-devel@m.gmane.org; Fri, 08 Nov 2019 14:49:38 +0100 Original-Received: from localhost ([::1]:54640 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iT4dt-0008M8-As for ged-emacs-devel@m.gmane.org; Fri, 08 Nov 2019 08:49:37 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:59551) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iT4dm-0008Lx-TL for emacs-devel@gnu.org; Fri, 08 Nov 2019 08:49:31 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:47916) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1iT4dm-0007m5-Hq; Fri, 08 Nov 2019 08:49:30 -0500 Original-Received: from [176.228.60.248] (port=3572 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1iT4dj-0005Qe-Q4; Fri, 08 Nov 2019 08:49:30 -0500 In-reply-to: (message from Jean-Christophe Helary on Fri, 8 Nov 2019 21:23:00 +0900) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:241981 Archived-At: > From: Jean-Christophe Helary > Date: Fri, 8 Nov 2019 21:23:00 +0900 > > > This isn't about importance, this is about potential slowdown in > > displaying a simple integer result because Emacs needs to look for a > > suitable font. > > Ok, so there are no needs whatsoever to display *any* character when evaluating an integer, am I correct ? There are situations where it is useful. For example: M-: (char-after) RET > Also, eval-expression-print-maximum-character is described in "24.9 Evaluating Emacs Lisp Expressions" but unlike eval-expression-print-length and eval-expression-print-level it is not indexed in the elisp reference even though both are also described only in that same chapter. Is that an oversight ? I don't think it's an oversight. This is a user option, so its place is generally on the user manual. The ELisp manual has a cross-reference to where that variable is described; the ELisp manual mentions eval-expression-print-length and eval-expression-print-level only because they are relevant to print-length and print-eval described there.