From: Richard Lawrence <richard.lawrence@berkeley.edu>
To: emacs-orgmode@gnu.org
Subject: Re: Large LaTeX project in single file or using publishing
Date: Fri, 28 Nov 2014 16:21:55 -0800 [thread overview]
Message-ID: <87k32eua8s.fsf@berkeley.edu> (raw)
In-Reply-To: 87vblzhxzr.fsf@wmi.amu.edu.pl
Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:
> 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).
Yes, that's a good point: if you already know LaTeX well, but are less
comfortable hacking on Org, that would probably change my advice.
I have accumulated about 600 lines of custom Elisp that is required to
export my thesis from Org to LaTeX and PDF. (The bulk of this, 471
lines, is a custom export backend derived from the latex backend. It
deals with exporting certain Org lists as non-standard LaTeX
environments. Most of the rest deals with exporting my reading list to
.bib and defining various custom link types, etc. to make the Org side
more pleasant.)
By contrast, I have only written about 100 lines in custom LaTeX style
files (so far -- I might need to do more of this when it comes time to
get the final styling right for filing my dissertation). I also rely on
other packages from CTAN, but I don't have to maintain those myself.
I'm no Elisp wizard, but I am now pretty familiar with Org exporter and
I'm comfortable with Lisp in general. On the other hand, I tend to shy
away from anything more complicated that \newcommand in the (La)TeX
world.
Best,
Richard
next prev parent reply other threads:[~2014-11-29 0:23 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 [this message]
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=87k32eua8s.fsf@berkeley.edu \
--to=richard.lawrence@berkeley.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).