From: Noam Postavsky <npostavs@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
18059@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#18059: 24.3.92; defvar and special variables
Date: Wed, 21 Feb 2018 13:00:49 -0500 [thread overview]
Message-ID: <CAM-tV-8zYVQy-7LQN9e1H7VznHpkJx6uDUe07JYLhFT_L=qB1Q@mail.gmail.com> (raw)
In-Reply-To: <ec1791e9-cb80-497d-bf00-45df246b374a@default>
On Wed, Feb 21, 2018 at 12:15 PM, Drew Adams <drew.adams@oracle.com> wrote:
>> Also, to clarify, I meant specifically non-toplevel (defvar foo), not
>> (defvar foo <value>).
>
> Too bad I didn't get your reply until after I spent time
> digging out the latter, not the former.
Yeah, I broke my rule about not sending a reply immediately. If I had
waited with the draft a bit more, I probably would have included the
clarification in the first message.
> Not to mention lots of vacuous defvars to quiet the byte-compiler:
>
> (unless (> emacs-major-version 22)
> (defvar display-buffer-reuse-frames))
So here, what is the use of putting it below the toplevel? Why don't
you just write
(defvar display-buffer-reuse-frames) ; For Emacs 22 and earlier.
> I have FAR MORE examples of the former (vacuous defvars)
> if you really need them.
I'd like to see more examples only if they would come with different
answers to my question above (why not write it at toplevel).
Otherwise, no need to repeat yourself.
Do you have any examples of the form (let (...) (defvar foo) ...)?
That's really where the troublesome behaviour that I'm hesitating to
document comes in.
next prev parent reply other threads:[~2018-02-21 18:00 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAM-tV-8zYVQy-7LQN9e1H7VznHpkJx6uDUe07JYLhFT_L=qB1Q@mail.gmail.com' \
--to=npostavs@gmail.com \
--cc=18059@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=michael_heerdegen@web.de \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.