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: Thu, 14 Nov 2019 11:22:41 +0200 Message-ID: <83zhgy7qxq.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> <835zjucwbz.fsf@gnu.org> <628A3663-BDD3-47C5-B4F4-E260FD900691@traduction-libre.org> <83o8xla50f.fsf@gnu.org> <8336ex9sow.fsf@gnu.org> <4836980E-C425-466C-BB86-5E962C4B3F96@traduction-libre.org> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="256279"; 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 Thu Nov 14 10:26:34 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 1iVBOZ-0014Wu-3n for ged-emacs-devel@m.gmane.org; Thu, 14 Nov 2019 10:26:31 +0100 Original-Received: from localhost ([::1]:54724 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iVBOX-0005kq-W1 for ged-emacs-devel@m.gmane.org; Thu, 14 Nov 2019 04:26:30 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:59990) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iVBL9-000452-Qk for emacs-devel@gnu.org; Thu, 14 Nov 2019 04:23:01 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:46931) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1iVBL9-0000a6-7D; Thu, 14 Nov 2019 04:22:59 -0500 Original-Received: from [176.228.60.248] (port=2944 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1iVBL7-0006MR-QI; Thu, 14 Nov 2019 04:22:58 -0500 In-reply-to: <4836980E-C425-466C-BB86-5E962C4B3F96@traduction-libre.org> (message from Jean-Christophe Helary on Sun, 10 Nov 2019 09:59:14 +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:242136 Archived-At: > From: Jean-Christophe Helary > Date: Sun, 10 Nov 2019 09:59:14 +0900 > > For "discoverability" (or "cognitive gap reduction") purposes, I'd rather have something like > > 1114111 (#o4177777, #x10ffff, t) > > 232 (#o350, #xe8, t) > > or something similar where t is the value of characterp for that integer when the integer is above the value of eval-expression-print-maximum-character. IMO, this would be extremely confusing. We don't have any other APIs like that, and using characterp in this case,m if appropriate, is very easy. So I very much dislike this proposal, especially since the solution is easy, and was already pointed out: customize that option.