From: Michael Heerdegen <michael_heerdegen@web.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 34233@debbugs.gnu.org,
Sebastian Miele <sebastian.miele@gmail.com>,
Stefan Monnier <monnier@IRO.UMontreal.CA>
Subject: bug#34233: 27.0.50; defvar in comment
Date: Tue, 09 Jul 2019 20:49:11 +0200 [thread overview]
Message-ID: <875zobdowo.fsf@web.de> (raw)
In-Reply-To: <87o923qdrm.fsf@mouse.gnus.org> (Lars Ingebrigtsen's message of "Tue, 09 Jul 2019 20:11:25 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Sebastian Miele <sebastian.miele@gmail.com> writes:
>
> > ;; Start ./src/emacs -Q, put this into *scratch*, do not remove this
> > ;; "(defvar x)" in this comment, and C-x C-e the following two
> > ;; expressions in turn:
> > ;;
> > (setq lexical-binding t)
> > (let ((x 42)) (lambda () x))
> > ;;
> > ;; Value: (closure (x t) nil x)
> > ;; Expected: (closure ((x . 42) t) nil x)
>
> I can confirm that this bug is still present.
>
> Stefan, do you know what's going on here? That a commented-out (defvar)
> before the eval-ed form has any effect is rather surprising...
This is `eval-sexp-add-defvars' not checking if defvars are really code.
Michael.
next prev parent reply other threads:[~2019-07-09 18:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 8:51 bug#34233: 27.0.50; defvar in comment Sebastian Miele
2019-07-09 18:11 ` Lars Ingebrigtsen
2019-07-09 18:49 ` Michael Heerdegen [this message]
2019-07-10 11:42 ` Lars Ingebrigtsen
2019-07-10 11:49 ` Noam Postavsky
2019-07-11 13:45 ` Lars Ingebrigtsen
2019-07-14 1:42 ` Noam Postavsky
2019-07-10 21:17 ` Michael Heerdegen
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=875zobdowo.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=34233@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@IRO.UMontreal.CA \
--cc=sebastian.miele@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 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).