From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: Large LaTeX project in single file or using publishing
Date: Fri, 28 Nov 2014 21:36:37 +0000 [thread overview]
Message-ID: <oluoarr2eje.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: 87vblzhxzr.fsf@wmi.amu.edu.pl
Hi Marcin,
Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:
> On 2014-11-27, at 10:26, Andreas Leha wrote:
>
>> Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:
>>>
>>> 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.
>> And preview-latex is really speeding me up.
>
> You're right, mostly. My point was that with displayed equations (in
> amsmath, since core LaTeX lacks a lot in this department), AUCTeX has at
> least one nice thing: C-u C-c C-e. (Also, plain C-c C-e.) Both very
> handy. (As for preview-LaTeX; in AUCTeX, you also have folding, which
> looks worse, but is faster - at least I guess so, I hardly ever use it.)
>
> (C-c C-e inserts an environment, with autocompletion. With prefix
> argument it /changes/ the surrounding environment.)
>
Are you aware of org-cdlatex-mode [1]? That provides some similar
functionality.f
> Also, Richard's post made me realize why I prefer to stay with LaTeX: I
> know it way better than Elisp (even though I'm making progress), and in
> case of troubles, I can more easily deal with them in LaTeX (though
> vertical positioning of things on the page - especially trying to
> typeset on a grid - still beats me).
I agree here. And some of my org documents admittedly look more like
latex documents ...
Best,
Andreas
[1] http://orgmode.org/manual/CDLaTeX-mode.html#CDLaTeX-mode
next prev parent reply other threads:[~2014-11-28 21:36 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 [this message]
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=oluoarr2eje.fsf@med.uni-goettingen.de \
--to=andreas.leha@med.uni-goettingen.de \
--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).