emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Kitchin <johnrkitchin@gmail.com>
To: "François Pinard" <pinard@iro.umontreal.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: Seeking advice for conditional code
Date: Thu, 31 Jan 2013 13:55:38 -0500	[thread overview]
Message-ID: <m1boc5gp1x.fsf@gilgamesh.cheme.cmu.edu> (raw)
In-Reply-To: <86lib96zzl.fsf@iro.umontreal.ca> ("François Pinard"'s message of "Thu, 31 Jan 2013 12:09:34 -0500")

I think I have done something like this with tags and custom export
lisp code.

Something like:

(let ((org-export-exclude-tags '("supplementary" "noexport")))
     (org-export-as-latex 5))

That allows me to export all sections not tagged by those values. This
would require all your code blocks be in tagged sections, e.g. tagged by
"internal", "external", etc...

for a particular org file I make an init.el file with different export
functions in it. Alternatively, I have put emacs-lisp code blocks in the
org file so it is self contained.

I am curious what other people do. My typical uses for selective export
are to selectively export a manuscript from an org file, or to
separately export a homework and the solution from one file.
-- 
==================================
John Kitchin
Associate Professor
A207F Doherty Hall
Department of Chemical Engineering
Carnegie Mellon University
412-268-7803

  reply	other threads:[~2013-01-31 18:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-31 17:09 Seeking advice for conditional code François Pinard
2013-01-31 18:55 ` John Kitchin [this message]
2013-01-31 21:03 ` Sebastien Vauban
2013-01-31 22:09   ` François Pinard
2013-01-31 22:56     ` Sebastien Vauban
2013-02-01  2:25       ` François Pinard
2013-02-01  8:24         ` Sebastien Vauban
2013-02-02  0:46           ` 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=m1boc5gp1x.fsf@gilgamesh.cheme.cmu.edu \
    --to=johnrkitchin@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=pinard@iro.umontreal.ca \
    /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).