emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: suvayu ali <fatkasuvayu+linux@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>, "Thomas S. Dye" <tsd@tsdye.com>
Subject: Re: Selective export of Babel code blocks
Date: Tue, 19 Jun 2012 08:36:49 -0500	[thread overview]
Message-ID: <CA+M2ft83GWrKj-=3qZFhaX+639WwR0V7155onmJqKmhVtrKM8g@mail.gmail.com> (raw)
In-Reply-To: <CAMXnza2f8ed==1xsVOmDvSAp0FTQ8-qcL3Ltsd6jpfnfmYf6Fg@mail.gmail.com>

On Tue, Jun 19, 2012 at 7:55 AM, suvayu ali <fatkasuvayu+linux@gmail.com> wrote:
> Hi Tom,
>
> On Mon, Jun 18, 2012 at 9:05 PM, Thomas S. Dye <tsd@tsdye.com> wrote:
>>
>> The :noweb header argument can take several values to control when these
>> noweb references are expanded.  Many of these don't show in the Org-mode
>> manual on Worg.  Here they are in org.texi:
>
>
> [...]
>
> I had missed these options! "no-export" might be the way to go. In any
> case, there seems to be a myriad of ways to go about this. The choice
> depends on John's preferences. :)

Indeed! Thanks for all the options. I haven't gotten to plugging in my
actual code yet but will try these ways and get back to the list!

Thanks all!
John

>
> Cheers,
>
> --
> Suvayu
>
> Open source is the future. It sets us free.

      reply	other threads:[~2012-06-19 13:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-18 14:53 Selective export of Babel code blocks John Hendy
2012-06-18 16:08 ` suvayu ali
2012-06-18 16:50   ` John Hendy
2012-06-18 17:08     ` suvayu ali
2012-06-18 17:37       ` William LÉCHELLE
2012-06-18 17:11 ` Thomas S. Dye
2012-06-18 17:16   ` suvayu ali
2012-06-18 17:31     ` John Hendy
2012-06-18 18:06       ` Andreas Leha
2012-06-18 19:05     ` Thomas S. Dye
2012-06-19 12:55       ` suvayu ali
2012-06-19 13:36         ` John Hendy [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='CA+M2ft83GWrKj-=3qZFhaX+639WwR0V7155onmJqKmhVtrKM8g@mail.gmail.com' \
    --to=jw.hendy@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=fatkasuvayu+linux@gmail.com \
    --cc=tsd@tsdye.com \
    /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).