From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Berry, Charles" <ccberry@ucsd.edu>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: Irrelevant src blocks can break noweb expansion
Date: Tue, 12 Dec 2017 08:42:55 +0100 [thread overview]
Message-ID: <87o9n4wfwg.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <E943FD29-0356-45E8-BB77-79DE3C785767@ucsd.edu> (Charles Berry's message of "Mon, 11 Dec 2017 03:13:41 +0000")
Hello,
"Berry, Charles" <ccberry@ucsd.edu> writes:
> I used to avoid this by `(setq org-babel-use-quick-and-dirty-noweb-expansion t)'.
>
> This illustrates the issue:
>
> #+begin_src org
>
> ,* abc
>
> ,#+begin_src R :comment (message "running on empty")
>
> ,#+end_src
>
> ,#+begin_src R :noweb yes
> 1
> ,#+end_src
>
>
> #+end_src
>
> The irrelevant, unnamed, empty src block its consulted via
> org-babel-get-src-block-info.
When? AFAICT, the second block doesn't contain any Noweb reference, so
there is nothing to consult in the first place. IOW, something is
missing in your recipe.
Also, `org-babel-use-quick-and-dirty-noweb-expansion' was intended to
skip properties check when collecting Noweb references from the buffer.
I.e., Org would only trust "name" keyword and ":noweb-ref" header
argument. Since there is no property in your example, I fail to see why
`org-babel-use-quick-and-dirty-noweb-expansion' would apply here.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2017-12-12 7:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 3:13 Irrelevant src blocks can break noweb expansion Berry, Charles
2017-12-12 7:42 ` Nicolas Goaziou [this message]
2017-12-12 16:13 ` Berry, Charles
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=87o9n4wfwg.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=ccberry@ucsd.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).