From: Eli Zaretskii <eliz@gnu.org>
To: No Wayman <iarchivedmywholelife@gmail.com>,
Lars Ingebrigtsen <larsi@gnus.org>,
Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 70868@debbugs.gnu.org
Subject: bug#70868: 30.0.50; pp--insert-lisp prints small integers as characters
Date: Sat, 11 May 2024 09:47:33 +0300 [thread overview]
Message-ID: <86ttj43kvu.fsf@gnu.org> (raw)
In-Reply-To: <878r0h8ayk.fsf@gmail.com> (message from No Wayman on Fri, 10 May 2024 20:10:43 -0400)
> From: No Wayman <iarchivedmywholelife@gmail.com>
> Date: Fri, 10 May 2024 20:10:43 -0400
>
> No Wayman <iarchivedmywholelife@gmail.com> writes:
>
> > From the body of pp--insert-lisp in pp.el:
> >
> >
> > ```emacs-lisp
> > ;; Print some of the smaller integers as characters, perhaps?
> > (integer
> > (if (<= ?0 sexp ?z)
> > (let ((print-integers-as-characters t))
> > (princ sexp (current-buffer)))
> > (princ sexp (current-buffer))))
> > ```
> >
> > I stumbled on this behavior in a program of which pretty prints
> > elisp forms as
> > part of a report.
> > I don't want characters when the input form originally included
> > integers.
> > Why do we do this here? The commentary doesn't offer any insight
> > and sounds
> > confused about the behavior, too.
> > Is it worth making configurable, or outright removing?
>
> A side-effect that tilts me in favor of removing said behavior:
>
> $ emacs -q --batch --eval '(pp-emacs-lisp-code `(:comments 59))'
>
> Error: scan-error ("Unbalanced parentheses" 1 16)
> forward-sexp-default-function(1)
> forward-sexp(1)
> indent-sexp()
> pp-emacs-lisp-code((:comments 59))
> eval((pp-emacs-lisp-code `(:comments 59)) t)
> command-line-1(("--eval" "(pp-emacs-lisp-code `(:comments
> 59))"))
> command-line()
> normal-top-level()
> Scan error: "Unbalanced parentheses", 1, 16
Lars and Stefan, any comments?
next prev parent reply other threads:[~2024-05-11 6:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 23:56 bug#70868: 30.0.50; pp--insert-lisp prints small integers as characters No Wayman
2024-05-11 0:10 ` No Wayman
2024-05-11 6:47 ` Eli Zaretskii [this message]
2024-05-11 10:58 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-11 11:09 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-11 12:08 ` Mattias Engdegård
2024-05-11 14:48 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-11 15:10 ` Mattias Engdegård
2024-05-11 11:32 ` Andreas Schwab
2024-05-11 10:54 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-11 16:38 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-11 16:47 ` Eli Zaretskii
2024-05-11 18:26 ` bug#70868: 30.0.50; iarchivedmywholelife
2024-05-11 18:29 ` Eli Zaretskii
2024-05-11 18:33 ` Eli Zaretskii
2024-05-12 14:50 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-12 15:06 ` Eli Zaretskii
2024-05-12 15:15 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-12 15:42 ` Eli Zaretskii
2024-05-12 18:11 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-28 10:51 ` bug#70868: 30.0.50; pp--insert-lisp prints small integers as characters Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-12 21:39 ` bug#70868: 30.0.50; Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-14 18:25 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-14 22:30 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-14 18:28 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-14 20:16 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=86ttj43kvu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=70868@debbugs.gnu.org \
--cc=iarchivedmywholelife@gmail.com \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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.