From: Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org>
To: Emacs developers <emacs-devel@gnu.org>
Subject: Re: evaluating numbers
Date: Thu, 14 Nov 2019 20:36:29 +0900 [thread overview]
Message-ID: <B6B06F8F-F302-4A4C-AACC-C650070691D7@traduction-libre.org> (raw)
In-Reply-To: <CAP_d_8Vzw_Xk=7xQZ942t2AdwBHUZmiQCRy4W_5mFrh+TexvNw@mail.gmail.com>
> On Nov 14, 2019, at 18:46, Yuri Khan <yuri.v.khan@gmail.com> wrote:
>
> On Thu, 14 Nov 2019 at 16:26, Eli Zaretskii <eliz@gnu.org> wrote:
>
>>> 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, if appropriate, is very
>> easy.
>
> A non-confusing solution to the issue “I have a code point and I’d
> like to know which character that is, but I don’t want Emacs to spend
> time trying all fonts to see if any of them has a glyph” could be to
> show the Unicode name for code points greater than
> eval-expression-print-maximum-character and less than (max-char).
>
> 232 (#o350, #xe8, LATIN SMALL LETTER E WITH GRAVE)
> 1114109 (#o4177775, #x10fffd, <Plane 16 Private Use>)
Yes !!! :)
Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune
next prev parent reply other threads:[~2019-11-14 11:36 UTC|newest]
Thread overview: 95+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 9:43 evaluating numbers Jean-Christophe Helary
2019-11-07 9:57 ` Stephen Berman
2019-11-07 10:20 ` Jean-Christophe Helary
2019-11-07 10:30 ` Stephen Berman
2019-11-07 10:40 ` Jean-Christophe Helary
2019-11-07 14:39 ` Eli Zaretskii
2019-11-08 0:36 ` Jean-Christophe Helary
2019-11-08 10:03 ` Eli Zaretskii
2019-11-08 12:23 ` Jean-Christophe Helary
2019-11-08 13:22 ` Stefan Monnier
2019-11-09 0:20 ` Jean-Christophe Helary
2019-11-09 7:24 ` Eli Zaretskii
2019-11-08 13:49 ` Eli Zaretskii
2019-11-09 0:15 ` Jean-Christophe Helary
2019-11-09 7:22 ` Eli Zaretskii
2019-11-09 11:18 ` Jean-Christophe Helary
2019-11-09 11:48 ` Eli Zaretskii
2019-11-10 0:59 ` Jean-Christophe Helary
2019-11-10 8:06 ` Andreas Schwab
2019-11-10 20:52 ` Juri Linkov
2019-11-12 20:28 ` Juri Linkov
2019-11-12 22:05 ` Drew Adams
2019-11-12 22:21 ` Eli Zaretskii
2019-11-12 23:30 ` Drew Adams
2019-11-13 8:10 ` Eli Zaretskii
2019-11-13 14:47 ` Drew Adams
2019-11-14 12:45 ` Eli Zaretskii
2019-11-14 22:50 ` Juri Linkov
2019-11-14 23:40 ` Noam Postavsky
2019-11-15 8:14 ` Eli Zaretskii
2019-11-14 9:22 ` Eli Zaretskii
2019-11-14 9:46 ` Yuri Khan
2019-11-14 11:36 ` Jean-Christophe Helary [this message]
2019-11-14 13:55 ` Stefan Monnier
2019-11-14 13:59 ` Noam Postavsky
2019-11-14 14:17 ` Stefan Monnier
2019-11-14 21:44 ` Juanma Barranquero
2019-11-14 14:03 ` Andreas Schwab
2019-11-14 14:10 ` Eli Zaretskii
2019-11-14 17:10 ` Paul Eggert
2019-11-14 18:32 ` Eli Zaretskii
2019-11-14 18:39 ` Eli Zaretskii
2019-11-15 8:32 ` Štěpán Němec
2019-11-15 14:54 ` Robert Pluim
2019-11-15 15:16 ` Eli Zaretskii
2019-11-15 15:32 ` Eli Zaretskii
2019-11-15 15:55 ` Robert Pluim
2019-11-15 16:00 ` Robert Pluim
2019-11-15 16:11 ` Lars Ingebrigtsen
2019-11-15 16:33 ` Robert Pluim
2019-11-15 16:13 ` Eli Zaretskii
2019-11-17 2:15 ` Richard Stallman
2019-11-17 20:02 ` Robert Pluim
2019-11-18 16:25 ` Eli Zaretskii
2019-11-18 16:54 ` Robert Pluim
2019-11-18 17:05 ` Eli Zaretskii
2019-11-20 13:00 ` Robert Pluim
2019-11-20 16:40 ` Eli Zaretskii
2019-11-20 17:09 ` Robert Pluim
2019-11-20 17:45 ` Eli Zaretskii
2019-11-19 6:08 ` Richard Stallman
2019-11-19 9:50 ` Robert Pluim
2019-11-15 15:53 ` Robert Pluim
2019-11-15 16:13 ` Eli Zaretskii
2019-11-15 16:43 ` Robert Pluim
2019-11-15 16:59 ` Eli Zaretskii
2019-11-16 20:40 ` Juri Linkov
2019-11-17 17:34 ` Eli Zaretskii
2019-11-17 21:16 ` Juri Linkov
2019-11-14 22:56 ` Juri Linkov
2019-11-09 16:03 ` Stefan Monnier
2019-11-10 0:22 ` Jean-Christophe Helary
2019-11-10 4:47 ` Stefan Monnier
2019-11-13 23:02 ` Jean-Christophe Helary
2019-11-14 13:52 ` Stefan Monnier
2019-11-14 9:20 ` Eli Zaretskii
2019-11-14 11:35 ` Jean-Christophe Helary
2019-11-14 13:37 ` Noam Postavsky
2019-11-14 14:20 ` Eli Zaretskii
2019-11-15 10:36 ` Jean-Christophe Helary
2019-11-15 13:03 ` Eli Zaretskii
2020-04-28 14:52 ` Jean-Christophe Helary
2020-04-28 15:05 ` Eli Zaretskii
2020-04-28 17:28 ` Paul Eggert
2020-04-28 23:16 ` Jean-Christophe Helary
2020-04-29 0:08 ` Paul Eggert
2020-04-29 0:21 ` Jean-Christophe Helary
2020-04-29 7:08 ` Eli Zaretskii
2020-04-29 8:00 ` Jean-Christophe Helary
2020-04-29 3:23 ` Richard Stallman
2020-04-29 3:49 ` Jean-Christophe Helary
2020-04-29 3:51 ` Stefan Monnier
2020-04-29 10:09 ` Po Lu
2020-04-30 2:34 ` Richard Stallman
2020-04-30 3:04 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B6B06F8F-F302-4A4C-AACC-C650070691D7@traduction-libre.org \
--to=jean.christophe.helary@traduction-libre.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.