emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: tsd@tsdye.com (Thomas S. Dye)
To: Jacob Gerlach <jacobgerlach@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Large LaTeX project in single file or using publishing
Date: Wed, 26 Nov 2014 09:47:34 -1000	[thread overview]
Message-ID: <m2h9xliw15.fsf@tsdye.com> (raw)
In-Reply-To: <CAA6UvuHB_WuMUYWmFKT7ipYe4aViAQbioxAMOEFTU_RJ3TQ1iQ@mail.gmail.com> (Jacob Gerlach's message of "Wed, 26 Nov 2014 19:00:36 +0000")

Aloha Jake,

In my experience, the one file approach is easiest with Org mode.  I've
written a book in Org mode using this approach and found it to be quite
comfortable.  Compilation time wasn't ever a big deal for me, but this
will depend on your patience obviously.

I don't think there are any real pitfalls, where you run into a
situation that can't be remedied.  The various LaTeX constructs in Org
mode let you apply LaTeX solutions at several scales, from snippets to
blocks, and these work well in my experience.

We use LaTeX at work and it would be easy for me to do my writing
outside work in LaTeX, but I now do all my outside work in Org mode.
The combination of Babel and the new exporter, along with the
integration of tools such as ebib, make this a congenial document
preparation environment.

hth,
Tom

Jacob Gerlach <jacobgerlach@gmail.com> writes:

> Hello list,
>
> I'm starting writing my thesis, for which I hope to remain in org-mode
> rather than regular LaTeX.
>
> I am working on adapting a thesis LaTeX template into org-mode. The
> template is set up with a main.tex having several individual files
> (chapters, appendices, etc) \include'd.
>
> I believe that I could parallel this using org's publishing mechanism. An
> alternate approach would be to use one single file, since I can simply fold
> chapters to focus my workflow.
>
> My first concern is losing the ability to use internal links if I use
> separate files. Another thought is compilation time if I use one file and
> must always run pdflatex over the entire document. I'm sure there are
> pitfalls either way that I'm not yet aware of.
>
> Any input or advice you can provide would be greatly appreciated.
>
> Regards,
> Jake
> Hello list,
>
> I'm starting writing my thesis, for which I hope to remain in org-mode
> rather than regular LaTeX.
>
> I am working on adapting a thesis LaTeX template into org-mode. The
> template is set up with a main.tex having several individual files
> (chapters, appendices, etc) \include'd.
>
> I believe that I could parallel this using org's publishing mechanism.
> An alternate approach would be to use one single file, since I can
> simply fold chapters to focus my workflow.
>
> My first concern is losing the ability to use internal links if I use
> separate files. Another thought is compilation time if I use one file
> and must always run pdflatex over the entire document. I'm sure there
> are pitfalls either way that I'm not yet aware of.
>
> Any input or advice you can provide would be greatly appreciated.
>
> Regards,
> Jake
>

-- 
Thomas S. Dye
http://www.tsdye.com

  parent reply	other threads:[~2014-11-26 19:48 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-26 19:00 Large LaTeX project in single file or using publishing Jacob Gerlach
2014-11-26 19:31 ` Scott Randby
2014-11-26 19:47 ` Thomas S. Dye [this message]
2014-11-27  7:51 ` Marcin Borkowski
2014-11-27  9:26   ` Andreas Leha
2014-11-28 20:27     ` Marcin Borkowski
2014-11-28 21:36       ` Andreas Leha
2014-11-28 22:16         ` Marcin Borkowski
2014-11-29  0:21       ` Richard Lawrence
2014-11-29  2:20         ` Andreas Leha
2014-11-29  3:48     ` Jorge A. Alfaro-Murillo
2014-11-29 11:55       ` Marcin Borkowski
2014-11-29 17:30         ` Jorge A. Alfaro-Murillo
2014-11-29 22:32           ` Marcin Borkowski
2014-11-27 10:09 ` Eric S Fraga
2014-11-28 20:41   ` Marcin Borkowski
2014-11-28 20:57     ` Eric S Fraga
2014-11-29  2:38     ` Jacob Gerlach
2014-11-29  3:23       ` Richard Lawrence
2014-12-03 20:24       ` Eric S Fraga
2014-11-27 11:43 ` Rainer M Krug
2014-11-28 17:40 ` Richard Lawrence
2014-11-28 18:49   ` Melleus
2014-11-28 20:32   ` Marcin Borkowski

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=m2h9xliw15.fsf@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jacobgerlach@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 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).