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 20:32:29 +0200 Message-ID: <83lfsi48ci.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> <83zhgy7qxq.fsf@gnu.org> <83lfsi5z1s.fsf@gnu.org> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="249554"; mail-complaints-to="usenet@blaine.gmane.org" Cc: jean.christophe.helary@traduction-libre.org, emacs-devel@gnu.org, yuri.v.khan@gmail.com To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Nov 14 19:33:43 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 1iVJw3-0012gd-Fy for ged-emacs-devel@m.gmane.org; Thu, 14 Nov 2019 19:33:39 +0100 Original-Received: from localhost ([::1]:60590 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iVJw1-0001EC-PE for ged-emacs-devel@m.gmane.org; Thu, 14 Nov 2019 13:33:37 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47352) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iVJvC-0001Cm-DZ for emacs-devel@gnu.org; Thu, 14 Nov 2019 13:32:47 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:57197) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1iVJvB-0005sM-14; Thu, 14 Nov 2019 13:32:45 -0500 Original-Received: from [176.228.60.248] (port=1067 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1iVJvA-0006Ao-En; Thu, 14 Nov 2019 13:32:44 -0500 In-reply-to: (message from Paul Eggert on Thu, 14 Nov 2019 09:10:02 -0800) 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:242189 Archived-At: > Cc: jean.christophe.helary@traduction-libre.org, emacs-devel@gnu.org > From: Paul Eggert > Date: Thu, 14 Nov 2019 09:10:02 -0800 > > On 11/14/19 6:10 AM, Eli Zaretskii wrote: > >> 232 (#o350, #xe8, LATIN SMALL LETTER E WITH GRAVE) > >> 1114109 (#o4177775, #x10fffd, ) > > I don't think this is less confusing, and I'm not really interested in > > opening that old debate again. The train has left the station, so > > people who are unhappy with the current defaults should customize the > > option we provided back then. > > Although I agree this topic has been discussed a lot, I wouldn't be so > hasty to reject Yuri's suggestion. I don't see how to customize Emacs so > that eval-expression outputs a string like "232 (#o350, #xe8, LATIN > SMALL LETTER E WITH GRAVE)". The behavior that Yuri's suggesting would > be more convenient to me than what Emacs currently does, as I often deal > with characters where it's more important to know the character's name > than what it looks like. I don't see the harm of adding this feature to > eval-expression by default, or at least as an option. Sorry, I don't want to make user-visible enhancements in this feature which has barely debuted. I would like to collect more user input first. FWIW, my personal opinion is that it's jarring to see something like "LATIN SMALL LETTER E WITH GRAVE" when all I asked was to evaluate an integer expression. (Showing the corresponding character is also jarring, but it's much less prominent, and it was there for a long time.) So the next we will hear is how to customize this not to show the character's name, etc. etc. Let's stop the feature creep right here, even though it's tempting (it always is).