From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Tom Gillespie <tgbugs@gmail.com>, Eli Zaretskii <eliz@gnu.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, 04 Jun 2022 21:47:55 +0800 [thread overview]
Message-ID: <87o7z81qwk.fsf@yahoo.com> (raw)
In-Reply-To: <87v8tg5z5y.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 04 Jun 2022 15:35:53 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> I've certainly been puzzled over the printed representation of these
> symbols, and I've wondered whether I should use a transliteration scheme
> (which isn't necessary), so I think it's likely that others have been,
> too.
Fulfilling a niche is not really a good enough reason to make such a
change, especially once it causes actual problems for someone.
Most programmers will not see a symbol with a dot inside every day, or
even every month (the ones you sent are the first ones I've seen this
year.) Programmers probably come across reasons to use them even less,
and the amount of those reasons is reduced even further if you rule out
unambiguous interfaces such as `intern'.
> Users will inevitably see symbols like this at some point or another.
Chances are (if it actually happens) those symbols will not be printed,
but displayed to the user as the product of something similar to:
(message "%s" 'symbol.here)
Which does not escape the dot.
That aside, why is it escaping a rarely encountered character inside a
symbol a "problem" important enough to fix, especially when the fix
breaks someone's code badly enough for him to complain about it?
next prev parent reply other threads:[~2022-06-04 13:47 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 [this message]
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
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=87o7z81qwk.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=55645@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
--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.