From: Robert Pluim <rpluim@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: master 4895ca16f7: Ensure that we don't call print-unreadable-function from " prin1"
Date: Thu, 28 Jul 2022 12:37:24 +0200 [thread overview]
Message-ID: <87czdpldzv.fsf@gmail.com> (raw)
In-Reply-To: <87y1wdwmu6.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 28 Jul 2022 12:30:57 +0200")
>>>>> On Thu, 28 Jul 2022 12:30:57 +0200, Lars Ingebrigtsen <larsi@gnus.org> said:
Lars> Robert Pluim <rpluim@gmail.com> writes:
>> If itʼs truly internal we should `unintern' it, no?
Lars> I didn't know that was possible?
DEFSYM (Qinternal_interpreter_environment,
"internal-interpreter-environment");
DEFVAR_LISP ("internal-interpreter-environment",
Vinternal_interpreter_environment,
doc: /* If non-nil, the current lexical environment of the lisp interpreter.
When lexical binding is not being used, this variable is nil.
A value of `(t)' indicates an empty environment, otherwise it is an
alist of active lexical bindings. */);
Vinternal_interpreter_environment = Qnil;
/* Don't export this variable to Elisp, so no one can mess with it
(Just imagine if someone makes it buffer-local). */
Funintern (Qinternal_interpreter_environment, Qnil);
Robert
--
next prev parent reply other threads:[~2022-07-28 10:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <165900384926.31041.14812200639744652787@vcs2.savannah.gnu.org>
[not found] ` <20220728102410.1F26BC0F1EF@vcs2.savannah.gnu.org>
2022-07-28 10:28 ` master 4895ca16f7: Ensure that we don't call print-unreadable-function from " prin1" Robert Pluim
2022-07-28 10:30 ` Lars Ingebrigtsen
2022-07-28 10:37 ` Robert Pluim [this message]
2022-07-28 10:40 ` Lars Ingebrigtsen
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=87czdpldzv.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
/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).