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: Sat, 29 Nov 2014 12:30:19 -0500 [thread overview]
Message-ID: <87k32ddidw.fsf@yale.edu> (raw)
In-Reply-To: 87egsmi5kt.fsf@wmi.amu.edu.pl
Marcin Borkowski writes:
> I mostly agree, but the above is not true: see TeX-pin-region
> and TeX-command-region. Bottom line: IMHO no point in dividing
> into many files.
You are right, you can compile a region in AUCTeX, or export just
a region in org, but the problem (besides having to select the
region as compared to a fast C-c C-c C-m) is that the result does
not have the whole document, just the part you selected, so you
miss seeing the exported part in context. For example, you miss
the ability to read before or after in the pdf and use a backward
search to find the code that corresponds to the next part that you
want to edit. If you use a main file plus several files in LaTeX,
the whole document is preserved but the compilation just runs in
the files with changes, and the backward search from the pdf
points to the right point in the right file (at least with evince
it does).
Best,
--
Jorge.
next prev parent reply other threads:[~2014-11-29 17:28 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 [this message]
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=87k32ddidw.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).