all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Douglas Lewan <d.lewan2000@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Compiling a recursive macro
Date: Thu, 11 Jun 2020 18:21:55 -0400	[thread overview]
Message-ID: <36ad9384-bfe0-e250-153e-e5872e99dc65@gmail.com> (raw)
In-Reply-To: <87ftb1469o.fsf@web.de>

On 6/11/20 5:55 PM, Michael Heerdegen wrote:
> Douglas Lewan <d.lewan2000@gmail.com> writes:
>
>> The macro itself has to establish a new variable for each buffer in
>> the tree of buffers.
> Are these variables buffer-local?  If not - could you use an alist with
> buffers being the keys instead and save that in one variable?  Why do
> you want one declared variable per buffer?
They are buffer-local. Definition of such a variable spans the tree of 
buffers in question. I suppose I could just define them in the root 
buffer, but then I'd also need to use a specialized getter instead of 
the variable itself. The latter definitely seems preferable to me. If 
there's a way to do this with emacs lisp's natural scoping, I'm more 
than happy to learn.

-- 
,Doug
d.lewan2000@gmail.com
(908) 720 7908

If this is what winning looks like, I'd hate to see what losing is.




  reply	other threads:[~2020-06-11 22:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-11 20:15 Compiling a recursive macro Douglas Lewan
2020-06-11 20:57 ` Stefan Monnier
2020-06-11 21:23   ` Douglas Lewan
2020-06-11 21:32     ` Michael Heerdegen
2020-06-11 21:38       ` Douglas Lewan
2020-06-11 21:55         ` Michael Heerdegen
2020-06-11 22:21           ` Douglas Lewan [this message]
2020-06-12 10:49             ` Michael Heerdegen
2020-06-12 16:11               ` Douglas Lewan
2020-06-12  2:10           ` Douglas Lewan
2020-06-13  9:49             ` Michael Heerdegen
2020-06-13 13:34               ` Jakub Jankiewicz
2020-06-11 22:02     ` Stefan Monnier
2020-06-11 21:27   ` Michael Heerdegen
2020-06-12  0:03 ` Jakub Jankiewicz

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=36ad9384-bfe0-e250-153e-e5872e99dc65@gmail.com \
    --to=d.lewan2000@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /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.