emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Fraga <e.fraga@ucl.ac.uk>
To: Keith <kigiokli@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Some settings are missing while exporting included org files to the tex file
Date: Sun, 29 Apr 2012 18:56:14 +0930	[thread overview]
Message-ID: <8762cianyh.fsf@ucl.ac.uk> (raw)
In-Reply-To: <4F8D6E2F.3070908@gmail.com> (Keith's message of "Tue, 17 Apr 2012 15:20:47 +0200")

Keith <kigiokli@gmail.com> writes:

> Dear Org-mode users:
> Recently I am considering using org-mode to write my thesis and would 
> like to separate each chapter into a single file. In order to do so, I 
> created a file gathering all the rest files like this:


> In addition, I also tried to export a single org file without any 
> preamble to be able to use input/include in latex but with no luck. And 
> it seems org mode does not support this function yet. I would recommend 
> the development team to re-consider this feature. Now the tex output of 
> org mode draws all the separate files into single tex file and the user 
> has to compile the entire tex file every time. By doing so, it also 
> misses the feature of LaTex as mentioned here: 
> http://web.science.mq.edu.au/~rdale/resources/writingnotes/latexstruct.html


I cannot help you with the bulk of your email, regarding the use of
#+include to bring in different chapters etc into a document and/or the
possibility of working on each individual chapter in turn.

However, because of these limitations, that I also ran into a long time
ago, I simply put everything into one document.  The advice given in the
web page noted above is directed at LaTeX but is less necessary for org
files.  The motivation is the need or desire to work on smaller bits at
a time to have things go quicker, I believe.  The easy way to handle
this in org is to use selective exporting, primarily through the use of

So, for instance, if I am working on a long document and am currently
working on chapter 2 of this document, my document would look like this:

| ...                                     |
| #+EXPORT_SELECT_TAGS: export            |
| #+EXPORT_EXCLUDE_TAGS: noexport         |
| ...                                     |
| * Introduction ...           :noexport: |
| * Chapter 1 ...              :noexport: |
| * Chapter 2                             |
| ...                                     |
| * Chapter 3 ...              :noexport: |
| ...                                     |

When asking for an export, only Chapter 2 would be exported.

It is trivial to add/remove the noexport tags.

The only difficulty with this arises when you need latex material at the
*end* of the document, such as bibliography settings.  For this, I
simply create a final "* Postamble" section which is exported.  When my
document is finished, I simply remove the heading line and re-export the
whole document.

A minor irritation appears if you have cross-references between chapters
but that really is nothing more than an irritation so I have learnt to
ignore it.


: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs
: using Org release_7.8.09-414-gb3e8a8

      reply	other threads:[~2012-04-29  9:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-17 13:20 Some settings are missing while exporting included org files to the tex file Keith
2012-04-29  9:26 ` Eric Fraga [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:

  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=8762cianyh.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=kigiokli@gmail.com \


* 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


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).