emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jarmo Hurri <jarmo.hurri@syk.fi>
To: emacs-orgmode@gnu.org
Subject: Re: Exporting book handouts
Date: Mon, 04 Nov 2013 15:01:06 +0200	[thread overview]
Message-ID: <87y5545njh.fsf@syk.fi> (raw)
In-Reply-To: m1iow9s3qj.fsf@tsdye.com


tsd@tsdye.com (Thomas S. Dye) writes:

> Aloha Jarmo,

Greetings to Hawaii from the dark and cold north.

> I find it easiest to use separate sub-trees for the various different
> documents I create from a given body of material.  In your case, I
> would make a sub-tree for the book and a sub-tree for the handout.  If
> I try to create two different documents under the same heading, the
> complexity overwhelms me.

I can also foresee problems with interleaving two documents, but I will
take some complexity over duplication any day. However, your approach
with named elements and reusable functions does appeal to me.

What is the mechanism you use to select the subtrees that you are
exporting? Are you employing SELECT_TAGS or something else?

> Where possible, I #+name: the elements that will be used in more than
> one place and then use #+call: lines to place them where I want.  

Great tip, thanks.

> I don't know off-hand the full list of elements that can be named and
> echoed this way.

I am in the process of starting to write a new section, so I will try it
out. For equations etc. it would also be possible to define LaTeX macros
for reuse.

Thanks a lot!

Jarmo

  reply	other threads:[~2013-11-04 13:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-03 16:54 Exporting book handouts Jarmo Hurri
2013-11-03 19:08 ` Thomas S. Dye
2013-11-04 13:01   ` Jarmo Hurri [this message]
2013-11-04 16:34     ` Thomas S. Dye
2013-11-03 19:15 ` Nicolas Goaziou
2013-11-04 13:19   ` Jarmo Hurri

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=87y5545njh.fsf@syk.fi \
    --to=jarmo.hurri@syk.fi \
    --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).