From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: :noweb header argument
Date: Tue, 10 Jan 2012 09:04:35 +0100 [thread overview]
Message-ID: <801ur8rnjg.fsf@somewhere.org> (raw)
In-Reply-To: m139bpaja0.fsf@tsdye.com
[-- Attachment #1: Type: text/plain, Size: 1405 bytes --]
Hi Thomas,
Thomas S. Dye wrote:
> Is there a difference between :noweb tangle and :noweb no?
Yes: ":noweb no" is the default, and must *not expand* anything.
> Based on the documentation and some limited testing, I made the following
> table.
>
> *** :noweb parameters
>
> | param | eval | tangle | export |
> |--------+------+--------+--------|
> | yes | + | + | + |
> | no | - | + | - |
It should be "-", "-", "-" here, if "-" means "no expansion".
> | tangle | - | + | - |
> |--------+------+--------+--------|
> | need | + | + | - |
>
> I think it might be good to have a parameter that expands noweb
> references on evaluation and tangling, but leaves them alone during
> export. This way the code block would be fully functional, but wouldn't
> duplicate code during export (when the noweb references are to other
> code blocks in the same document).
I'd find that interesting as well, but then the names of the code blocks must
be visible again (in HTML and PDF exports), something that has disappeared
over time.
Find attached the 2 PDF I had written (in 2009) for comparing NoWeb's
rendering of blocks and Babel's rendering. See
http://lists.gnu.org/archive/html/emacs-orgmode/2009-12/msg00170.html.
Some time after that, we had block names in the HTML/PDF output, but not
anymore.
Best regards,
Seb
--
Sebastien Vauban
[-- Attachment #2: ecm-babel-org.pdf --]
[-- Type: application/pdf, Size: 78164 bytes --]
[-- Attachment #3: ecm-noweb.pdf --]
[-- Type: application/pdf, Size: 96058 bytes --]
next prev parent reply other threads:[~2012-01-10 8:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-08 23:04 :noweb header argument Thomas S. Dye
2012-01-10 8:04 ` Sebastien Vauban [this message]
2012-01-10 8:24 ` Andreas Leha
2012-01-10 11:30 ` Eric S Fraga
2012-01-10 15:41 ` Thomas S. Dye
2012-01-10 16:44 ` Eric Schulte
2012-01-10 18:42 ` Thomas S. Dye
2012-01-11 8:09 ` Sebastien Vauban
2012-01-11 15:06 ` Eric S Fraga
2012-01-14 19:59 ` Eric Schulte
2012-01-14 23:06 ` Thomas S. Dye
2012-01-15 15:28 ` Eric Schulte
2012-01-18 10:03 ` Eric S Fraga
2012-01-18 19:11 ` Yagnesh Raghava Yakkala
2012-01-11 17:17 ` Eric Schulte
2012-01-10 21:04 ` Eric S Fraga
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=801ur8rnjg.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).