From: Jacob Gerlach <jacobgerlach@gmail.com>
To: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Large LaTeX project in single file or using publishing
Date: Fri, 28 Nov 2014 21:38:32 -0500 [thread overview]
Message-ID: <CAA6UvuFDHSJVUxYi+yZ0wG36yizY22h8Rd8S_RyR5O9BzXvpJw@mail.gmail.com> (raw)
In-Reply-To: <87sih3hxcq.fsf@wmi.amu.edu.pl>
Wow, I expected a little help, but never to spark such a conversation.
Thanks to all for the comments.
Thanks to all who suggested sticking with one file. That was the main
issue I needed to sort out, and I'm glad I have a way foward
On Wed, Nov 26, 2014 at 2:31 PM, Scott Randby <srandby@gmail.com> wrote:
> You don't have to compile the whole document every time. You can
> export a subtree: C-c C-e, C-s changes the export scope.
I had never tried out this feature before. I had previously customized
org-latex-link-with-unknown-path-format to help me catch link
typos [1], which causes subtree (pdf) export to fail if it includes a link
that is out of scope. Nevertheless, I may come back to this and adjust
the behavior if I end up having problems with export time.
On Thu, Nov 27, 2014 at 2:51 AM, Marcin Borkowski <mbork@wmi.amu.edu.pl> wrote:
> On Wednesday, 26 Nov 2014 at 19:00, Jacob Gerlach wrote:
>> 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.
>
> Is that required in any way? I'd be surprised if it was.
Not at all required. I'm working from an already-created template
that meets the format requirements. The template is set up with
separate files. All that's required is the final pdf format.
> (FYI: you can also fold things in AUCTeX.)
Didn't realize that, but I'll probably stick with Org for now!
On Thu, Nov 27, 2014 at 5:09 AM, Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
> For me, the killer feature is the ability to put inline tasks in the
> document so that I know what I need to work on without having to have a
> separate task list or todo items within my general day to day task
> list. Then a simple "C-c / t" shows me all the tasks for the current
> document.
Thus far I've mostly used Org as a LaTeX editor and haven't really
taken the time to learn and use the task tracking, but I really like
this idea. I haven't looked, but I'm sure there are variables to
control whether TODO state gets exported.
On Thu, Nov 27, 2014 at 6:43 AM, Rainer M Krug <Rainer@krugs.de> wrote:
> Don't forget latexmk which runns in an emacs shell or even a
> different terminal, monitors file changes, and if a file changes
> compiles the latex file - so exporting from org is exporting to latex
> only, and the pdf is creqated in the background.
Inded, I have org-latex-pdf-process set to:
("latexmk -f -pdf %f" "latexmk -f -pdf %f")
And I always export directly to pdf.
> I use it daily and it works perfectly.
I often find that latexmk fails to resolve links after I've made some
minor changes to a document. I haven't put much effort into troubleshooting
this - I end up running pdflatex over the file 2 extra times. I
suppose I should add that to org-latex-pdf-process...
On Fri, Nov 28, 2014 at 12:40 PM, Richard Lawrence
<richard.lawrence@berkeley.edu> wrote:
> Here are a couple of other things to think about. When I decided to go
> with Org, I took a few steps to ensure that if I ever need to switch to
> pure LaTeX, I will be able to do so with minimal pain, just by exporting
> my Org document to .tex and going from there. (The big sticking point
> here for me was making sure I could produce human-readable, stable
> labels and refs for things like sections. See the variable
> org-latex-custom-id-as-label, which was introduced by a patch I wrote.)
This sounds helpful. I'm using ELPA (tracking maint?) and don't see
this variable. Was your patch applied to master?
> Another thing to think ahead about is how you want to deal with your
> bibliography. People on this list use different approaches. I
> personally keep my reading tasks and notes in Org, then generate a .bib
> file from this as needed during compilation of my thesis. Others keep
> bibliographic information directly in .bib. I think you'll find there
> are good tools for either approach, but one or the other will probably
> fit better into your workflow, and may affect how easily you can export
> to other formats.
Yes, I know I have a lot to figure out in this arena. That's another day...
[1] http://lists.gnu.org/archive/html/emacs-orgmode/2014-08/msg00681.html
next prev parent reply other threads:[~2014-11-29 2:38 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
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 [this message]
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=CAA6UvuFDHSJVUxYi+yZ0wG36yizY22h8Rd8S_RyR5O9BzXvpJw@mail.gmail.com \
--to=jacobgerlach@gmail.com \
--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).