unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Alan Mackenzie <acm@muc.de>, 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 12:43:29 -0800 (PST)	[thread overview]
Message-ID: <256f068f-5a0a-4127-aa7c-633eae24f15f@default> (raw)
In-Reply-To: <jwvk14qntnk.fsf-monnier+emacs@gnu.org>

> > Can we please fix the doc, to make things clear?
> 
> I added:
> 
>   Note that since this is a function, it can only return
>   non-@code{nil} for variables which are permanently special, but not
>   for those that are only special in the current lexical scope.

Thanks very much for working on this.

But I'm afraid I don't know what a permanent versus
temporary special variable is.  And I haven't found
anything in the doc that has helped me with that.

I looked in Elisp nodes `Using Lexical Binding',
where `special-variable-p' is documented, and
`Defining Variables', where `defvar' is doc'd.
"special" variable seems to be defined as a term
in each of those nodes, BTW.  (I also looked in
node `Variable Scoping'.)

Node `Defining Variables' seems to say that using
`defvar' is enough to make a variable "always"
dynamic:

  The variable is marked as "special", meaning
  that it should always be dynamically bound
                 ^^^^^^
  (*note Variable Scoping::).

Is "always" something different from "permanent"?

Sorry, but I really don't understand what is meant
by what you wrote.  I also don't understand the
implication, "since this is a function".
              ^^^^^
But maybe that's because I don't understand
"permanently special" and "only special in the
current lexical scope".

AFAIK, in Common Lisp a variable is either special
or it's not.  If it is then its binding by `let'
is dynamic, and if it's not then its let-binding
is lexical. (No?)



  reply	other threads:[~2020-02-13 20:43 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
2020-02-13 20:02               ` Stefan Monnier
2020-02-13 20:43                 ` Drew Adams [this message]
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=256f068f-5a0a-4127-aa7c-633eae24f15f@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).