[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: evaluating numbers
From: |
Eli Zaretskii |
Subject: |
Re: evaluating numbers |
Date: |
Thu, 14 Nov 2019 11:22:41 +0200 |
> From: Jean-Christophe Helary <address@hidden>
> 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.
- Re: evaluating numbers, (continued)
- Re: evaluating numbers, Juri Linkov, 2019/11/12
- RE: evaluating numbers, Drew Adams, 2019/11/12
- RE: evaluating numbers, Eli Zaretskii, 2019/11/12
- RE: evaluating numbers, Drew Adams, 2019/11/12
- RE: evaluating numbers, Eli Zaretskii, 2019/11/13
- RE: evaluating numbers, Drew Adams, 2019/11/13
- 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 <=
- Re: evaluating numbers, Yuri Khan, 2019/11/14
- Re: evaluating numbers, Jean-Christophe Helary, 2019/11/14
- Re: evaluating numbers, Stefan Monnier, 2019/11/14
- 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