[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: evaluating numbers
From: |
Stefan Monnier |
Subject: |
Re: evaluating numbers |
Date: |
Thu, 14 Nov 2019 08:55:20 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
> 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>)
To the extent that "LATIN SMALL LETTER E WITH GRAVE" can't be used to
write 232 I don't like this suggestion, but I think you're on to
something: what if eval-expression-print-maximum-character was used only
to decide between `?<CHAR>` and `?\u<HEX>` ?
Stefan
- RE: evaluating numbers, (continued)
- Re: evaluating numbers, Eli Zaretskii, 2019/11/14
- Re: evaluating numbers, Juri Linkov, 2019/11/14
- Re: evaluating numbers, Noam Postavsky, 2019/11/14
- Re: evaluating numbers, Eli Zaretskii, 2019/11/15
- Re: evaluating numbers, Eli Zaretskii, 2019/11/14
- Re: evaluating numbers, Yuri Khan, 2019/11/14
- Re: evaluating numbers, Jean-Christophe Helary, 2019/11/14
- Re: evaluating numbers,
Stefan Monnier <=
- Re: evaluating numbers, Noam Postavsky, 2019/11/14
- Re: evaluating numbers, Stefan Monnier, 2019/11/14
- Re: evaluating numbers, Juanma Barranquero, 2019/11/14
- Re: evaluating numbers, Andreas Schwab, 2019/11/14
- Re: evaluating numbers, Eli Zaretskii, 2019/11/14
- Re: evaluating numbers, Paul Eggert, 2019/11/14
- Re: evaluating numbers, Eli Zaretskii, 2019/11/14
- Re: evaluating numbers, Eli Zaretskii, 2019/11/14
- Re: evaluating numbers, Štěpán Němec, 2019/11/15
- Re: evaluating numbers, Robert Pluim, 2019/11/15