From: Drew Adams <drew.adams@oracle.com>
To: Stephen Berman <stephen.berman@gmx.net>,
Noam Postavsky <npostavs@users.sourceforge.net>
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
Tino Calancha <f92capac@gmail.com>,
23781@debbugs.gnu.org
Subject: bug#23781: 25.0.95; read-string with HIST lexically bound
Date: Sat, 25 Jun 2016 14:00:32 -0700 (PDT) [thread overview]
Message-ID: <fd7b8f13-cf50-429b-8441-32c7271fedbc@default> (raw)
In-Reply-To: <8737o1w15d.fsf@gmx.net>
> Well, the info node `(elisp) Variables' says:
>
> In Lisp, each variable is represented by a Lisp symbol (see
> Symbols::). The variable name is simply the symbol’s name [...]
>
> and a symbol's name is a string (according to `symbol-name'). But maybe
> we should leave the bike shed before this gets too philosophical ;-)
That was written (and was true) back when Emacs had only dynamic
variables, that is, symbols that act as variables, with name
`symbol-name' and value `symbol-value'.
Unfortunately, the developer who added lexical binding to Emacs
Lisp was not very strong or motivated in the Doc department (by
his own admission), so that text was not amended. At least that's
my guess for why it still says that.
Section `Variable Scoping' was added to the manual to present
lexical binding. And there is some hint of it in node `Local
Variables'. The rest of the doc seems to generally be talking
about dynamic variables (even if local, buffer-local, file-local,
etc.).
next prev parent reply other threads:[~2016-06-25 21:00 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
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 [this message]
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
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=fd7b8f13-cf50-429b-8441-32c7271fedbc@default \
--to=drew.adams@oracle.com \
--cc=23781@debbugs.gnu.org \
--cc=f92capac@gmail.com \
--cc=michael_heerdegen@web.de \
--cc=npostavs@users.sourceforge.net \
--cc=stephen.berman@gmx.net \
/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).