From: jorge.alfaro-murillo@yale.edu (Jorge A. Alfaro-Murillo)
To: emacs-orgmode@gnu.org
Subject: Re: Large LaTeX project in single file or using publishing
Date: Fri, 28 Nov 2014 22:48:23 -0500 [thread overview]
Message-ID: <87oarqd5vc.fsf@yale.edu> (raw)
In-Reply-To: oluvbm12dw4.fsf@med.uni-goettingen.de
Andreas Leha writes:
> On 2014-11-26, at 20:00, Jacob Gerlach wrote:
>>
>> Just my 2 cents: I'd go for LaTeX if heavy math typesetting is
>> involved (then amsmath!), maybe for Org otherwise, check
>> whether the template imposes a many-file structure (which it
>> probably doesn't), and keep everything in one file.
>>
>
> I would disagree here. I do not see, that writing equations in
> LaTeX is substantially easier than in org. Or put the other way
> round: org's support for equations is quite good.
There is no way that writing equations can be faster in org than
in AUCTeX, since AUCTeX is designed for that, especially with
LaTeX-math-mode, two keys write any Greek symbol for example. And
all the support for completion of commands, environments and
environment variables, changing fonts, sectioning, integration
with reftex...
By the way, AUCTeX supports many packages by default including
amsmath, so just adding the proper \usepackage{amsmath} in the
preamble makes AUCTeX fontify in math-mode align, gather,
multline, and their starred equivalents.
The one thing that org is better at is tables, but for that I use
radiotables inside of AUCTeX.
> And preview-latex is really speeding me up.
I have never been a fan of preview or any WYSIWYG editing, I feel
like it slows me down, but if you use only org and are not used to
LaTeX it could be helpful, in AUCTeX it is easier to read math
because of the fonts used (for example subscripts and superscripts
are written under and over the symbols). I would also suggest
compiling with SyncTeX for forward search support, I do not know
if forward search is possible with org.
That being said there is a learning curve associated with
TeX/AUCTeX and if you are already very comfortable with org and do
not have time for learning something new, perhaps it is better to
stick with org.
If you decide to go with LaTeX, the reason to split your
dissertation in several chapters is so that the compilation can
run faster, since when you change a chapter and compile only that
chapter is compiled again. This is a substantial gain in
compilation time with big documents (books, dissertations). If you
decide to go with several org files and the publishing mechanism
or a single org file, I think that every time that you export the
whole document needs to be compiled.
Best,
--
Jorge.
next prev parent reply other threads:[~2014-11-29 3:46 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
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 [this message]
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=87oarqd5vc.fsf@yale.edu \
--to=jorge.alfaro-murillo@yale.edu \
--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).