From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Tino Calancha <f92capac@gmail.com>, 23781@debbugs.gnu.org
Subject: bug#23781: 25.0.95; read-string with HIST lexically bound
Date: Thu, 23 Jun 2016 19:01:51 -0400 [thread overview]
Message-ID: <CAM-tV--GxiuBi43ZFQ3bmZez=a+1aV4Ue_yGNdQPwPdD3Yc5Gg@mail.gmail.com> (raw)
In-Reply-To: <877fdn96sv.fsf@web.de>
On Fri, Jun 17, 2016 at 11:25 AM, Michael Heerdegen
<michael_heerdegen@web.de> wrote:
>
> AFAICT this is expected and not specific to `read-string': A quoted
> symbol can never refer to a lexical binding - and `symbol-value' or
> `eval' always return the dynamic binding.
Right, it's sort of hinted at in the elisp manual (11.9.3 Lexical Binding):
Note that functions like ‘symbol-value’, ‘boundp’, and ‘set’ only
retrieve or modify a variable’s dynamic binding (i.e., the
contents of its symbol’s value cell).
I think we should be a little more specific, not
just give examples, something like:
Note that functions which take a symbol argument (like
‘symbol-value’, ‘boundp’, and ‘set’) can only retrieve or modify a
variable’s dynamic binding (i.e., the contents of its symbol’s
value cell).
Sort of releated: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=21185
next prev parent reply other threads:[~2016-06-23 23:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 5:19 bug#23781: 25.0.95; read-string with HIST lexically bound Tino Calancha
2016-06-17 15:25 ` Michael Heerdegen
2016-06-23 23:01 ` Noam Postavsky [this message]
2016-06-23 23:18 ` Drew Adams
2016-06-25 0:26 ` Noam Postavsky
2016-06-25 10:12 ` Stephen Berman
2016-06-25 16:53 ` Noam Postavsky
2016-06-25 18:53 ` Stephen Berman
2016-06-25 19:46 ` Noam Postavsky
2016-06-25 22:07 ` Stephen Berman
2016-06-25 23:42 ` Michael Heerdegen
2016-06-26 3:34 ` Noam Postavsky
2016-06-27 0:55 ` Noam Postavsky
2016-07-01 4:07 ` npostavs
2016-06-26 2:23 ` Drew Adams
2016-06-25 21:00 ` Drew Adams
2016-06-25 20:42 ` Drew Adams
2016-06-24 2:24 ` Tino Calancha
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='CAM-tV--GxiuBi43ZFQ3bmZez=a+1aV4Ue_yGNdQPwPdD3Yc5Gg@mail.gmail.com' \
--to=npostavs@users.sourceforge.net \
--cc=23781@debbugs.gnu.org \
--cc=f92capac@gmail.com \
--cc=michael_heerdegen@web.de \
/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.