bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#31614: Off Topic (was: bug#31614)


From: Van L
Subject: bug#31614: Off Topic (was: bug#31614)
Date: Mon, 28 May 2018 21:05:35 +1000

> Eli Zaretskii writes:
> 
> You are saying that the Texinfo manual uses ASCII quotes, and therefore
> the opening and closing quotes are identical?  If so, the place to
> complain about that is the Texinfo mailing list.

The point of TeX is beautiful typesetting.

I don’t want to create another bug report for why

  (+ 2 2) 

gives the ``complication’’ by default

  4 (#o4, #x4, ?\C-d)

and not the simple

  4

Emacs 26.1-rc1 (NS Port) and Emacs 25.3 (Mac Port) both produce

  4 (#o4, #x4, ?\C-d)

In the below, it is not possible to set 
`eval-expression-print-maximum-character’ to `nil’ to 
achieve the simple `4’ result. 
`M-x customize’ wants a number for 26.1-rc1 and the default is 127. 

  #+NAME: simple.el.gz
  #+BEGIN_SRC elisp n=1535
    If the resulting value is an integer, and CHAR-PRINT-LIMIT is
    non-nil (interactively, unless given a positive prefix argument)
    it will be printed in several additional formats (octal,
    hexadecimal, and character).  The character format is only used
    if the value is below CHAR-PRINT-LIMIT (interactively, if the
    prefix argument is -1 or the value is below
    `eval-expression-print-maximum-character').

  #+END_SRC

  #+NAME: eval-expression-print-maximum-character
  #+BEGIN_EXAMPLE
    eval-expression-print-maximum-character is a variable defined in 
‘simple.el’.
    Its value is 127

    Documentation:
    The largest integer that will be displayed as a character.
    This affects printing by ‘eval-expression’ (via
    ‘eval-expression-print-format’).

    You can customize this variable.

    This variable was introduced, or its default value was changed, in
    version 26.1 of Emacs.

  #+END_EXAMPLE

The backtrace diff I submitted in another bug needs undoing 
because I believe the simple `4' result is better to keep in the earlier lisp 
intro.

Details about ``complications’’ is bulk the lisp intro can separate into a 
different book. 






reply via email to

[Prev in Thread] Current Thread [Next in Thread]