From: Greg Minshall <email@example.com>
To: Eric S Fraga <firstname.lastname@example.org>
Subject: Re: declaring :var in a property drawer
Date: Mon, 24 May 2021 12:22:42 +0300 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: Your message of "Mon, 24 May 2021 09:57:42 +0100." <firstname.lastname@example.org>
> I would suggest it is intentional: setting a header property means it
> applies to *all* src blocks.
thanks. but, in this case, all source blocks are being tangled to the
same file. which, for many (most?) languages (but not elisp), means the
variable is going to be defined (and re-defined) at (the particular
language's version of) global scope. which seems mostly redundant.
that was what i was wondering about.
prev parent reply other threads:[~2021-05-24 9:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-23 14:25 Greg Minshall
2021-05-24 8:57 ` Eric S Fraga
2021-05-24 9:22 ` Greg Minshall [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).