From: "Thomas S. Dye" <tsd@tsdye.com>
To: suvayu ali <fatkasuvayu+linux@gmail.com>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: exporting as latex sections
Date: Sat, 4 Dec 2010 15:51:25 -1000 [thread overview]
Message-ID: <B1C27300-D728-40F3-A533-B33494346D64@tsdye.com> (raw)
In-Reply-To: <AANLkTi=XrwmTrHQvTSNjmyeCRRNiv0beJ9OtEALZvhMz@mail.gmail.com>
Aloha Suvayu,
On Dec 3, 2010, at 4:26 PM, suvayu ali wrote:
> Hi org-mode users,
>
> I have been collaborating on a big (many contributors) paper. For all
> my various contributions to the paper I need to provide the latex
> source as a section of a latex document. Is there some way I can
> export to latex without all the preamble and header information from
> the org-mode file? Or just exporting to latex and manually removing
> all that is the only way to do it?
>
> While we are at it if I were to attempt to write my own version of
> latex export function which does this instead, where should I be
> looking? I'm not very good at lisp, so some suggestions would be
> really helpful if I need to take this route.
>
> Thanks for any help/suggestions.
>
> --
> Suvayu
I don't know any way to do this with the Org-mode LaTeX exporter
(though there may be some way I don't know yet).
This might not be an option you want to follow, or something you have
already thought about, but you could achieve your result using LaTeX
source code blocks and then tangle, rather than export, your
contribution. This has the advantage that it is relatively simple to
tangle different chunks, in case you are contributing to different
parts of the paper.
#+source: chunk1
#+begin_src latex :tangle chunk1.tex
This is chunk 1.
#+end_src
#+source: chunk2
#+begin_src latex :tangle chunk2.tex
This is chunk 2.
#+end_src
Hope this helps.
All the best,
Tom
next prev parent reply other threads:[~2010-12-05 1:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-04 2:26 exporting as latex sections suvayu ali
2010-12-05 1:51 ` Thomas S. Dye [this message]
2010-12-05 3:38 ` suvayu ali
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B1C27300-D728-40F3-A533-B33494346D64@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=fatkasuvayu+linux@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.