From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Tom Gillespie <tgbugs@gmail.com>, 55645@debbugs.gnu.org
Subject: bug#55645: src/print.c; print_object changes make it impossible to compare elisp code across versions
Date: Mon, 11 Jul 2022 13:22:45 +0200 [thread overview]
Message-ID: <87czebx5a2.fsf@gnus.org> (raw)
In-Reply-To: <83zgio5t52.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 07 Jun 2022 19:35:05 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> Of course you are wrong, since we changed prin1 without affecting
> read. We could also change both prin1 and read such that what the
> former produces the latter can consume, as long as the "usual" Lisp
> code can still be read without any problem.
This was a month ago, and I think the conclusion here is that we don't
want to add an option to tweak this printing behaviour (or guarantee
that we won't change printing in general), so I'm closing this bug
report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-07-11 11:22 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 23:12 bug#55645: src/print.c; print_object changes make it impossible to compare elisp code across versions Tom Gillespie
2022-05-26 12:03 ` Lars Ingebrigtsen
2022-05-26 15:56 ` Tom Gillespie
2022-05-27 10:33 ` Lars Ingebrigtsen
2022-05-27 19:19 ` Tom Gillespie
2022-05-28 10:39 ` Lars Ingebrigtsen
2022-05-28 17:54 ` Tom Gillespie
2022-05-29 13:15 ` Lars Ingebrigtsen
2022-05-29 15:14 ` Eli Zaretskii
2022-05-29 21:03 ` Tom Gillespie
2022-06-04 9:15 ` Eli Zaretskii
2022-06-04 11:35 ` Lars Ingebrigtsen
2022-06-04 11:53 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-04 12:09 ` Lars Ingebrigtsen
2022-06-04 12:18 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-04 13:14 ` Lars Ingebrigtsen
2022-06-04 13:30 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-04 13:35 ` Lars Ingebrigtsen
2022-06-04 13:47 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-06 23:30 ` Tom Gillespie
2022-06-07 16:35 ` Eli Zaretskii
2022-07-11 11:22 ` Lars Ingebrigtsen [this message]
2022-07-11 18:43 ` Tom Gillespie
2022-07-12 12:44 ` Lars Ingebrigtsen
2022-07-13 23:26 ` Tom Gillespie
2022-07-14 17:22 ` Lars Ingebrigtsen
2022-07-14 21:36 ` Tom Gillespie
2022-07-18 18:13 ` Tom Gillespie
2022-07-12 3:04 ` Richard Stallman
2022-07-12 12:45 ` Lars Ingebrigtsen
2022-07-13 3:16 ` Richard Stallman
2022-05-28 23:14 ` Richard Stallman
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=87czebx5a2.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=55645@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=tgbugs@gmail.com \
/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.