From: Greg Minshall <minshall@umich.edu>
To: emacs-orgmode@gnu.org
Subject: babel/noweb concatenation of equally-named code blocks fails?
Date: Sun, 19 Apr 2020 13:07:43 -0700 [thread overview]
Message-ID: <977659.1587326863@apollo2.minshall.org> (raw)
hi. the description of :noweb-ref says
----
When expanding “noweb” style references, the bodies of all code block
with _either_ a block name matching the reference name _or_ a
‘:noweb-ref’ header argument matching the reference name will be
concatenated together to form the replacement text.
----
plus, this (admittedly old) page suggests this concatenation should
happen:
----
http://eschulte.github.io/org-scraps/scraps/2011-06-10-continued-code-blocks.html
----
if i evaluate (C-c C-c) "tryxx" below on the 9.1.9 which is in my emacs
(26.3), i get two lines of output (as shown). if, using packages, i
"upgrade" to either of the following:
----
org 9.3.6 available gnu
org 20200413 available org
----
(and, also a 201912...), i only get the first output line ("in first
tryx"). (*tangling*, i get both code blocks.)
is the behavior in the newer versions intentional? or, should i file a
bug?
cheers, and thanks. and, these days, stay safe. Greg
---- cut here ---
** continued code blocks
#+property: header-args :noweb yes
#+name: tryx
#+begin_src R
cat("in first tryx\n")
#+end_src
#+name: tryx
#+begin_src R
cat("in second tryx\n")
#+end_src
#+name: tryxx
#+begin_src R :results output
<<tryx>>
#+end_src
#+RESULTS: tryxx
: in first tryx
: in second tryx
next reply other threads:[~2020-04-19 20:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 20:07 Greg Minshall [this message]
2020-04-19 21:11 ` babel/noweb concatenation of equally-named code blocks fails? Nicolas Goaziou
2020-04-19 21:18 ` Greg Minshall
2020-04-19 21:53 ` Nicolas Goaziou
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=977659.1587326863@apollo2.minshall.org \
--to=minshall@umich.edu \
--cc=emacs-orgmode@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 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).