From: Arthur Miller <arthur.miller@live.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Defvar not called at top level
Date: Thu, 25 Nov 2021 04:04:53 +0100 [thread overview]
Message-ID: <AM9PR09MB4977DE12CA8604E64694FD8A96629@AM9PR09MB4977.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <jwv1r35smjf.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 24 Nov 2021 08:38:22 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> Arthur Miller [2021-11-24 11:47:16] wrote:
>> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> Arthur Miller [2021-11-23 14:28:04] wrote:
>>>> Just a question: why is it important to call defvar from top level?
>>>> I would like to have some code that generates some other code, amongs that to
>>>> declare few global symbols with auto generated docs as well.
>>>
>>> Presumably you can do this with
>>>
>>> (defmacro FOO (..) ... `(defvar ...) ...)
>>>
>>> (FOO ...)
>>>
>>>> If I call those from a defun/macro normally I get that warning that defvar is
>>>> not called at top level;
>>>
>>> Can you show the actual warning?
>>
>>
>> Thank you for the answer; it seems like I can't :).
>>
>> I am sorry, I had too many things in my head and confused things. It was not
>> "defvar" it was "defvar-local". I appologize.
>
> So the warning was not about `defvar` but about `make-variable-buffer-local`.
Yes. Caused by defvar-locals I pasted in.
> The reason for this warning is to catch the widespread confusion between
> `make-variable-buffer-local` and `make-local-variable`.
Aha. I thought it was more like it's easy to create a binding in wrong buffer.
Anyway, thanks.
prev parent reply other threads:[~2021-11-25 3:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 13:28 Defvar not called at top level Arthur Miller
2021-11-23 13:58 ` Stefan Monnier
2021-11-24 10:47 ` Arthur Miller
2021-11-24 13:38 ` Stefan Monnier
2021-11-25 3:04 ` Arthur Miller [this message]
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=AM9PR09MB4977DE12CA8604E64694FD8A96629@AM9PR09MB4977.eurprd09.prod.outlook.com \
--to=arthur.miller@live.com \
--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).