emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Diego Zamboni <diego@zzamboni.org>
To: Org-mode <emacs-orgmode@gnu.org>
Subject: Exporting noweb-ref's without disabling org-babel processing
Date: Tue, 22 Oct 2019 22:29:08 +0200	[thread overview]
Message-ID: <CAGY83EfQuQ3c2VDVMeuUCMTF7NZqNL=5nEP+fojXcE2-PYPwYA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1614 bytes --]

Hi,

I'm working on a Leanpub Markua exporter (not quite complete yet but
already usable, if you are interested:
https://github.com/zzamboni/ox-leanpub/tree/book-and-markua)

I would like to include the value of :noweb-ref for code blocks in exported
output, like noweb originally did, e.g. something like this:

#begin_src emacs_lisp :noweb-ref super-duper-code
...
#end_src

to produce something like this in the export:

<<super-duper-code>>=
 ...

After much poking around, I figured that the :noweb and :noweb-ref header
args are removed by org-babel *before* the src block makes it to the
exporter. I also discovered that by setting org-export-use-babel to nil I
could disable this behavior, which means that my exporter can access the
:noweb-ref argument by parsing the :parameters property (see
https://github.com/zzamboni/ox-leanpub/blob/book-and-markua/ox-leanpub-markua.el#L388
).

This was good for my original purpose, but I just realized that this also
disables other useful org-babel features on export, such as the processing
of the :exports header argument, which means that both code and results are
always included in the export regardless of what :exports says :)

I have tried using org-babel-exp-code-template, but unfortunately if I try
to use "%noweb-ref" as a key in its value, it gets replaced by the value of
:noweb followed by "-ref" in every case.

Is there some other way of accessing org-babel header arguments like
:noweb-ref from the exporter, but without having to disable org-babel
processing completely? Any other ideas for achieving what I want?

Thanks for any ideas,
--Diego

[-- Attachment #2: Type: text/html, Size: 2143 bytes --]

             reply	other threads:[~2019-10-22 20:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-22 20:29 Diego Zamboni [this message]
2019-10-23 16:50 ` Exporting noweb-ref's without disabling org-babel processing Berry, Charles
2019-10-24 12:02   ` Diego Zamboni

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='CAGY83EfQuQ3c2VDVMeuUCMTF7NZqNL=5nEP+fojXcE2-PYPwYA@mail.gmail.com' \
    --to=diego@zzamboni.org \
    --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).