From: Drew Adams <drew.adams@oracle.com>
To: Noam Postavsky <npostavs@users.sourceforge.net>,
Stephen Berman <stephen.berman@gmx.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 13:42:52 -0700 (PDT) [thread overview]
Message-ID: <b5b9b94d-7edd-4333-b5a9-e9a295f984bd@default> (raw)
In-Reply-To: <CAM-tV--mkNNno6Vu+3Lassyqy0vEYtodxwErWLAoX0XeGZ0eRQ@mail.gmail.com>
> > I think it's more a question of definition than philosophy: AFAIU using
> > the word "symbols" here is strictly speaking incorrect; it should be
> > "variables".
>
> Yes, perhaps the implementation details leaked a bit too much into the
> description. I think it remains the case that the name of a variable
> is a symbol (as opposed to a string) though.
The _name_ of a variable is not a symbol.
A symbol is a Lisp object. It can have a name (`symbol-name'), a
value as a (dynamic) variable (`symbol-value'), a value as a
function (`symbol-function'), and a list of arbitrary Lisp values
(`symbol-plist').
Other kinds of programming variables also exist in Emacs Lisp,
including lexical variables. A `let' and similar constructs in
the language can bind a lexical variable or it can bind a dynamic
variable, that is, a symbol used as a variable. In the latter
case, the bound value is available as the symbol's `symbol-value'.
next prev parent reply other threads:[~2016-06-25 20:42 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
2016-06-25 20:42 ` Drew Adams [this message]
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=b5b9b94d-7edd-4333-b5a9-e9a295f984bd@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).