From: "Eric Schulte" <schulte.eric@gmail.com>
To: aditya siram <aditya.siram@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: [org-babel] :no-expand header expands noweb refs
Date: Wed, 06 Oct 2010 10:39:45 -0600 [thread overview]
Message-ID: <87d3rn8ecu.fsf@gmail.com> (raw)
In-Reply-To: <AANLkTintzXH_=mfSscWK9_nZ8W-k-YUJ1W4Sf4jZKQsS@mail.gmail.com> (aditya siram's message of "Tue, 5 Oct 2010 22:38:36 -0500")
Hi,
The ":noweb yes" header argument will expand noweb references during
both tangling and weaving. I've added another noweb header argument
"tangle" which will expand noweb header arguments during tangling but
not during weaving(export), so replacing ":noweb yes" with ":noweb
tangle" in your example below should result in the desired behavior.
Best -- Eric
aditya siram <aditya.siram@gmail.com> writes:
> It appears I misread the manual. 'no-expand' works only for tangling -
> but my original question stands. Is there a header that provides this
> feature for weaving with links to the chunk like a noweb document?
>
> -deech
>
> On Tue, Oct 5, 2010 at 10:12 PM, aditya siram <aditya.siram@gmail.com> wrote:
>> Hi all,
>> I may have understood the :no-expand header incorrectly, but I thought
>> it suppressed expanding noweb references while exporting but seems to
>> expand them.
>> For example I have an org file that looks like this (simplified) :
>> * Root
>> #+begin_src fundamental :noweb yes :no-expand :tangle Root.txt
>> <<Chunk1>>
>> <<Chunk2>>
>> #+end_src
>> * Chunk 1
>> #+source: Chunk1
>> #+begin_src fundamental
>> code for chunk 1
>> #+end_src
>> * Chunk 2
>> #+source: Chunk2
>> #+begin_src fundamental
>> code for chunk 2
>> #+end_src
>>
>> When I 'org-export-as-ascii-to-buffer' I expect this :
>> Root
>> ====
>>
>> Table of Contents
>> =================
>> ....
>>
>> 1 Root
>> ~~~~~~~
>> <<Chunk1>>
>> <<Chunk2>>
>> ...
>>
>> But I get this:
>> Root
>> ====
>>
>> Table of Contents
>> =================
>> 1 Root
>> 2 ...
>>
>>
>> 1 Root
>> ~~~~~~~
>>
>> code for chunk 1
>> code for chunk 2
>> ...
>>
>>
>> Thanks for the help!
>> -deech
>>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
prev parent reply other threads:[~2010-10-06 21:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 3:12 [org-babel] :no-expand header expands noweb refs aditya siram
2010-10-06 3:38 ` aditya siram
2010-10-06 16:39 ` Eric Schulte [this message]
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=87d3rn8ecu.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=aditya.siram@gmail.com \
--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).