From: Richard Stallman <rms@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 24982@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#24982: 24.5; way to let Elisp reader ignore unreadable #(...) constructs
Date: Sun, 13 Feb 2022 23:15:54 -0500 [thread overview]
Message-ID: <E1nJSmI-0001pP-Ij@fencepost.gnu.org> (raw)
In-Reply-To: <87zgmvxig4.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun, 13 Feb 2022 09:46:19 +0100)
[[[ 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. ]]]
> Anyway, there was some discussion about this in the context of the new
> readablep function and the `print-unreadable-function' variable. We
> could indeed introduce a new `read-unreadable-function' variable that's
> called when we encounter a #< instead of throwing an error (with no
> performance impact).
> Does anybody see any major downsides to doing that? We've been wary of
> allowing the users to customise the Emacs Lisp reader, but this seems
> like a very small thing. And it'd allow people to implement having
I think it is asking for trouble to make `read' extensible, because
then people will extend it in different, incompatible ways. That is
asking for trouble.
Uniformity is what we need here. If we want to handle some additional
read syntax, we should implement it in the C code so that it works the
same for everyone.
--
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)
next prev parent reply other threads:[~2022-02-14 4:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 21:47 bug#24982: 24.5; way to let Elisp reader ignore unreadable #(...) constructs Drew Adams
2018-04-02 19:32 ` Juri Linkov
2018-04-02 20:31 ` Drew Adams
2018-04-02 20:54 ` Juri Linkov
2018-04-02 21:32 ` Drew Adams
2018-04-03 20:06 ` Juri Linkov
2020-08-22 19:13 ` Stefan Kangas
2020-08-22 19:17 ` Lars Ingebrigtsen
2020-08-22 19:28 ` Drew Adams
2020-08-22 19:53 ` Lars Ingebrigtsen
2020-08-22 22:44 ` Drew Adams
2020-08-22 19:25 ` Drew Adams
2022-02-13 8:46 ` Lars Ingebrigtsen
2022-02-13 17:33 ` bug#24982: [External] : " Drew Adams
2022-02-13 17:53 ` Lars Ingebrigtsen
2022-02-13 18:03 ` Drew Adams
2022-02-14 4:15 ` Richard Stallman [this message]
2022-04-30 17:01 ` Lars Ingebrigtsen
2022-04-30 17:26 ` Drew Adams
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1nJSmI-0001pP-Ij@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=24982@debbugs.gnu.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).