From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Greg Minshall <minshall@umich.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: babel/noweb concatenation of equally-named code blocks fails?
Date: Sun, 19 Apr 2020 23:53:15 +0200 [thread overview]
Message-ID: <87eesjta5w.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <991128.1587331097@apollo2.minshall.org> (Greg Minshall's message of "Sun, 19 Apr 2020 14:18:17 -0700")
Greg Minshall <minshall@umich.edu> writes:
> Nicolas, thanks. i take it this is a change from (recent?) past
> behavior?
I think this was done between Org 9.1 and 9.2, the final step probably
being 99dbca3d4f2fb30f35309a0bf4c324535b7dc9f3
> it was kind of nice the old way, but i suspect i'll get used
> to the new way (no names, just noweb-ref) fairly soon.
Mixing noweb-ref and names slowed down Noweb expansion very much. We
papered over it using that odd variable:
`org-babel-use-quick-and-dirty-noweb-expansion'. IOW, you had to choose
between speed and accuracy when expanding Noweb blocks.
Now, this is simpler: using NAME keyword is the fast path, with a single
block. Using :noweb-ref is the slow path, but you can concatenate
multiple blocks.
next prev parent reply other threads:[~2020-04-19 21:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 20:07 babel/noweb concatenation of equally-named code blocks fails? Greg Minshall
2020-04-19 21:11 ` Nicolas Goaziou
2020-04-19 21:18 ` Greg Minshall
2020-04-19 21:53 ` Nicolas Goaziou [this message]
2020-04-19 23:06 ` Greg Minshall
2020-04-20 9:23 ` Nicolas Goaziou
2020-04-22 4:45 ` Greg Minshall
2020-04-22 10:50 ` Nicolas Goaziou
2020-04-22 14:22 ` Greg Minshall
2020-04-22 17:09 ` Nicolas Goaziou
2020-04-22 21:51 ` Greg Minshall
2020-04-23 8:43 ` Nicolas Goaziou
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eesjta5w.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=minshall@umich.edu \
/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/org-mode.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).