From: "Kevin M. Stout" <firstname.lastname@example.org>
Subject: Re: 2 Surprises and 2 Questions Regarding Org Tangle
Date: Fri, 12 Feb 2021 23:13:06 -0500 [thread overview]
Message-ID: <20210213041306.GA17795@cibola.cibola> (raw)
On 2021-02-11 18:44, Diego Zamboni wrote:
> #2 is known (maybe documented? Not sure) behavior: using :noweb-ref
> accumulates multiple blocks with the same name, whereas #+NAME uses only
> the first one. I think #+NAME's are supposed to be unique within a document.
It seems that more recent versions of org-babel-expand-noweb-references (not
org-babel-tangle, as I said in an earlier message) no longer accumulate blocks
with common #+NAMEs. (Now, though, #+NAME has priority over :noweb-ref, which is
the opposite of how things were done before.) Looking through some older
discussions on the topic, I do see the downsides of accepting duplicate #+NAMEs,
which are rooted in the assumption of uniqueness made elsewhere. Even so, I
still hold that
#+NAME: this is a cool way to do something
is a much nicer syntax than
#+BEGIN_SRC language :noweb-ref "this is a cool way to do something"
especially as a project grows.
Perhaps we could have a variation on #+NAME that doesn't need to be unique?
Maybe something like #+NOREF, to evoke :noweb-ref? Or #+NONAME?
Kevin M. Stout
next prev parent reply other threads:[~2021-02-13 4:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 12:29 2 Surprises and 2 Questions Regarding Org Tangle Lee Jia Hong
2021-02-11 17:44 ` Diego Zamboni
2021-02-13 2:41 ` Kevin M. Stout
2021-02-13 4:13 ` Kevin M. Stout [this message]
2021-02-11 17:46 ` Greg Minshall
2021-02-11 17:52 ` Greg Minshall
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).