From: Drew Adams <drew.adams@oracle.com>
To: Alan Mackenzie <acm@muc.de>, Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: RE: Can't M-x compile-defun `edebug' because dynamic variables are falsely taken as lexical.
Date: Thu, 13 Feb 2020 08:42:49 -0800 (PST) [thread overview]
Message-ID: <29855ded-8607-4132-a80f-3204c06d74d9@default> (raw)
In-Reply-To: <20170104200458.GA2052@acm.fritz.box>
Coming back to this old thread (2017).
sm> > special-variable-p only indicates if
sm> > (defvar VAR VAL . REST) was evaluated.
And not (defvar VAR), apparently?
am> So it would seem. There is a bug in the elisp manual, which says that a
am> variable being declared by defvar will cause special-variable-p to
am> return t for it. The doc string looks right, though far from helpful
am> for anybody who doesn't already know variable binding inside out, and
am> even a bit cryptic for those who do.
am>
am> special-variable-p would appear to be a near useless function, since it
am> doesn't do what it's name says.
am>
am> "Defining Variables" in the elisp manual states that "(defvar foo)" makes
am> foo a special variable; yet "(special-variable-p 'foo)" returns nil. This
am> has got to be a bug, of some sort.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
am> There appears to be no way of checking whether a variable's binding is
am> (or will be) lexical.
am>
am> I can foresee quite a bit of confusion happening over all this, if it
am> hasn't happened already.
am>
am> Am I missing something, or is this all really as incoherent as it
am> appears to me?
sm> It's useful for the compiler, but it's mostly internal, indeed.
Reading the doc, a user will have no idea that this
is "internal" mostly or not. And s?he will have no
idea why (defvar foo) (special-variable-p 'foo)
returns nil.
Can we please fix the doc, to make things clear?
If this function is really (or "mostly"?) internal
why document it in this way? Neither the manual
nor the doc string gives a clue about this.
Can we please get the doc to not mislead about this,
at least in some way?
next prev parent reply other threads:[~2020-02-13 16:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 14:14 Can't M-x compile-defun `edebug' because dynamic variables are falsely taken as lexical Alan Mackenzie
2017-01-03 18:35 ` Stefan Monnier
2017-01-03 21:32 ` Alan Mackenzie
2017-01-03 21:48 ` Stefan Monnier
2017-01-04 13:39 ` Alan Mackenzie
2017-01-04 15:23 ` Stefan Monnier
2017-01-04 20:04 ` Alan Mackenzie
2017-01-04 21:49 ` Stefan Monnier
2017-01-04 22:02 ` Alan Mackenzie
2017-01-04 22:26 ` Stefan Monnier
2017-01-04 22:44 ` Drew Adams
2017-01-05 10:54 ` Alan Mackenzie
2020-02-13 16:42 ` Drew Adams [this message]
2020-02-13 20:02 ` Stefan Monnier
2020-02-13 20:43 ` Drew Adams
2020-02-13 22:09 ` Stefan Monnier
2020-02-14 1:07 ` Drew Adams
2020-02-14 2:24 ` Stefan Monnier
2020-02-14 17:25 ` Drew Adams
2020-02-14 19:19 ` Stefan Monnier
2020-02-17 18:23 ` Drew Adams
2020-02-13 22:11 ` Stefan Monnier
2020-02-14 1:13 ` Drew Adams
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=29855ded-8607-4132-a80f-3204c06d74d9@default \
--to=drew.adams@oracle.com \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).