From: Richard Stallman <rms@gnu.org>
To: Tom Gillespie <tgbugs@gmail.com>
Cc: larsi@gnus.org, 55645@debbugs.gnu.org
Subject: bug#55645: src/print.c; print_object changes make it impossible to compare elisp code across versions
Date: Sat, 28 May 2022 19:14:15 -0400 [thread overview]
Message-ID: <E1nv5dP-0006p0-9T@fencepost.gnu.org> (raw)
In-Reply-To: <CA+G3_PN5Nx10+mAgt1VKA2Snfm34jHNSCiPS4BRY1s3w3LRWsA@mail.gmail.com> (message from Tom Gillespie on Fri, 27 May 2022 12:19:27 -0700)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> I was thinking the same. I realize that for many objects where
> there is no guarantee of homoiconicity the prin1 representation
> definitely changes all the time. However, I think that symbols
> fall into a more homoiconic category (namely the category
> of objects that can appear literally in code).
I agree.
We have no absolute rule against changing the print syntax of symbols,
but we see that it this change is likely to cause a real practical
disadvantage for some users. We should treat that as a significant
problem, and do what it takes to spare users that practical problem.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
prev parent reply other threads:[~2022-05-28 23:14 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
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 [this message]
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=E1nv5dP-0006p0-9T@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=55645@debbugs.gnu.org \
--cc=larsi@gnus.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.