From: iarchivedmywholelife <iarchivedmywholelife@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>,
Michael Heerdegen <michael_heerdegen@web.de>
Cc: 70868@debbugs.gnu.org
Subject: bug#70868: 30.0.50;
Date: Sat, 11 May 2024 14:26:07 -0400 [thread overview]
Message-ID: <663fb841.050a0220.ffcbb.b84f@mx.google.com> (raw)
In-Reply-To: <86plts1ej2.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]
I would expect/want no conversion in either case. Maybe instead of printing based purely off type we can see what how the data was represented and delegate based off that.
-------- Original message --------From: Eli Zaretskii <eliz@gnu.org> Date: 5/11/24 12:47 PM (GMT-05:00) To: Michael Heerdegen <michael_heerdegen@web.de> Cc: 70868@debbugs.gnu.org, iarchivedmywholelife@gmail.com Subject: Re: bug#70868: 30.0.50; > Cc: iarchivedmywholelife@gmail.com> Date: Sat, 11 May 2024 18:38:48 +0200> From: Michael Heerdegen via "Bug reports for GNU Emacs,> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>> > > Anyway, adding a user option will probably be the best solution we can> > implement.> > We already have `print-integers-as-characters', though. So if we want to> make this completely controllable on the per usage basis, removing those> lines would indeed make more sense. Then the user could just bind> `print-integers-as-characters' as for any other printing action.The issue here is user expectations from what Emacs does by default.To see what I mean, remove those lines, and then try M-: (pp-emacs-lisp-code '(eq foo ?a)) RETEvidently, there are two sides to this coin.
[-- Attachment #2: Type: text/html, Size: 1648 bytes --]
next prev parent reply other threads:[~2024-05-11 18:26 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
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 ` iarchivedmywholelife [this message]
2024-05-11 18:29 ` bug#70868: 30.0.50; 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=663fb841.050a0220.ffcbb.b84f@mx.google.com \
--to=iarchivedmywholelife@gmail.com \
--cc=70868@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=michael_heerdegen@web.de \
/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.