unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@gmail.com>
To: Van L <van@scratch.space>
Cc: 31614@debbugs.gnu.org
Subject: bug#31614: Off Topic
Date: Mon, 28 May 2018 07:30:11 -0400	[thread overview]
Message-ID: <877enodnlo.fsf@gmail.com> (raw)
In-Reply-To: <BC17175C-8CDE-47AF-9C21-E48F41A31334@scratch.space> (Van L.'s message of "Mon, 28 May 2018 21:05:35 +1000")

Van L <van@scratch.space> writes:

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

There's not really a reason not to, we won't run out of bug numbers.

>   (+ 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.

Oh, I think I intended eval-expression-print-maximum-character to only
affect the ?\C-d part, e.g., if you set it to 0, you get

    4 (#o4, #x4)

But I see there is no way to get a plain '4' except by (setq
eval-expression-print-maximum-character nil), which is kind of an
accident.





  reply	other threads:[~2018-05-28 11:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-28  3:56 bug#31614: (texinfo) dfn - the double quotes around ``deleting'' are inconsistent with (eintr) Complications ``variables'' Van L
2018-05-28  8:55 ` Eli Zaretskii
2018-05-28 11:05   ` bug#31614: Off Topic (was: bug#31614) Van L
2018-05-28 11:30     ` Noam Postavsky [this message]
2018-05-28 13:04       ` bug#31614: Off Topic Van L
2018-05-28 15:18       ` Eli Zaretskii
2018-05-28 15:37         ` Noam Postavsky
2018-05-28 15:15     ` bug#31614: Off Topic (was: bug#31614) Eli Zaretskii
2018-05-28 10:52 ` bug#31614: (texinfo) dfn - the double quotes around ``deleting'' are inconsistent with (eintr) Complications ``variables'' Andreas Schwab
2018-05-28 16:17   ` Eli Zaretskii
2022-02-07 10:06     ` Lars Ingebrigtsen

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877enodnlo.fsf@gmail.com \
    --to=npostavs@gmail.com \
    --cc=31614@debbugs.gnu.org \
    --cc=van@scratch.space \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).