From: Drew Adams <drew.adams@oracle.com>
To: Michael Heerdegen <michael_heerdegen@web.de>,
Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 18059@debbugs.gnu.org
Subject: bug#18059: 24.3.92; defvar and special variables
Date: Sat, 10 Feb 2018 16:17:33 -0800 (PST) [thread overview]
Message-ID: <22c4a80b-ae72-4c6b-b12e-0104bdea3e00@default> (raw)
In-Reply-To: <87y3k0bdm9.fsf@web.de>
> > +Note that specifying a value, even @code{nil}, marks the variable as
> > +special permanently. Whereas if @var{value} is omitted then the
> > +variable is only marked special locally (i.e. within the current file
> > +or let-block). This can be useful for suppressing byte compilation
> > +warnings, see @ref{Compiler Errors}.
>
> After reading this and thinking about it, I'm confused now what the
> extent of `defvar' without a specified value is.
>
> In the case of a file, does it mean that the variable is considered
> special for the rest of the file, or for the whole file?
Apologies for not following this. Question: is some change
in behavior being discussed here or is it just a question
about improving documentation of the longstanding behavior?
next prev parent reply other threads:[~2018-02-11 0:17 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-20 3:23 bug#18059: 24.3.92; defvar and special variables Michael Heerdegen
2018-02-10 19:29 ` Noam Postavsky
2018-02-10 23:59 ` Michael Heerdegen
2018-02-11 0:17 ` Drew Adams [this message]
2018-02-11 0:43 ` Noam Postavsky
2018-02-11 0:38 ` Noam Postavsky
2018-02-11 1:32 ` Michael Heerdegen
2018-02-11 2:26 ` Noam Postavsky
2018-02-11 15:14 ` Stefan Monnier
2018-02-11 15:35 ` Noam Postavsky
2018-02-11 16:38 ` Michael Heerdegen
2018-02-11 17:00 ` Noam Postavsky
2018-02-14 0:27 ` Noam Postavsky
2018-02-18 22:28 ` Noam Postavsky
2018-02-19 1:44 ` Michael Heerdegen
2018-02-21 15:09 ` Noam Postavsky
2018-02-21 16:08 ` Drew Adams
2018-02-21 16:23 ` Noam Postavsky
2018-02-21 16:33 ` Noam Postavsky
2018-02-21 17:15 ` Drew Adams
2018-02-21 18:00 ` Noam Postavsky
2018-02-21 19:14 ` Drew Adams
2018-02-21 19:19 ` Stefan Monnier
2018-02-21 22:20 ` Michael Heerdegen
2018-02-23 14:05 ` Stefan Monnier
2018-02-23 14:55 ` Michael Heerdegen
2018-03-04 23:27 ` Noam Postavsky
2018-03-05 9:51 ` Michael Heerdegen
2018-03-07 13:00 ` Noam Postavsky
2018-03-09 9:58 ` Michael Heerdegen
2018-03-09 13:43 ` Stefan Monnier
2018-03-11 16:45 ` Noam Postavsky
2018-03-11 22:16 ` Drew Adams
2018-03-14 11:15 ` Noam Postavsky
2018-03-23 12:23 ` Noam Postavsky
2018-03-05 15:57 ` Eli Zaretskii
2018-03-08 23:36 ` Noam Postavsky
2018-03-09 0:15 ` Drew Adams
2018-02-21 17:11 ` Drew Adams
2018-02-11 15:57 ` Eli Zaretskii
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=22c4a80b-ae72-4c6b-b12e-0104bdea3e00@default \
--to=drew.adams@oracle.com \
--cc=18059@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=npostavs@users.sourceforge.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).