From: Nick Dokos <nicholas.dokos@hp.com>
To: =?utf-8?Q?S=C3=A9bastien_Vauban?= <wxhgmqzgwmuf@spammotel.com>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: [PATCH] Compiling multiple times the LaTeX output
Date: Thu, 30 Sep 2010 11:39:05 -0400 [thread overview]
Message-ID: <30671.1285861145@gamaville.dokosmarshall.org> (raw)
In-Reply-To: Message from =?utf-8?Q?S=C3=A9bastien_Vauban?= <wxhgmqzgwmuf@spammotel.com> of "Thu\, 30 Sep 2010 15\:27\:49 +0200." <874od7uzsa.fsf_-_@mundaneum.com>
Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> wrote:
> Hi Noorul and all,
>
> Noorul Islam K M wrote:
> > Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> writes:
> >> I've been taught of a weird observation: the page number indicated in the
> >> TOC of a PDFLaTeX output is wrong by one page...
> >
> > Quoting from source code
> >
> > (defcustom org-latex-to-pdf-process
> > '("pdflatex -interaction nonstopmode -output-directory %o %f"
> > "pdflatex -interaction nonstopmode -output-directory %o %f")
> > "Commands to process a LaTeX file to a PDF file.
> > This is a list of strings, each of them will be given to the shell
> > as a command.
>
> Attached my proposed patch for fixing this, regarding the TOC error (needed a
> third compilation). Here, as many compilations as necessary are run, up to
> when LaTeX confirms the result is stable (no message "please re-run...").
>
I don't know if that's still the case, but there were (rare) situations where
that would *never* happen: LaTeX would oscillate between two different states
of output, so you always needed to do one more compilation. The only fix was
to rearrange the *input* sligthly to try to get LaTeX out of its rut.
It may be wise to limit the number of compilations to 3 (but perhaps make
it configurable, so that it can be increased if necessary).
Nick
next prev parent reply other threads:[~2010-09-30 15:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 14:25 Compiling multiple times the LaTeX output Sébastien Vauban
2010-09-29 15:17 ` Noorul Islam K M
2010-09-30 13:27 ` [PATCH] " Sébastien Vauban
2010-09-30 15:39 ` Nick Dokos [this message]
2010-09-30 16:55 ` Sébastien Vauban
2010-10-01 15:32 ` Thomas S. Dye
2010-10-01 21:17 ` Sébastien Vauban
2010-10-04 7:41 ` Carsten Dominik
2010-10-04 10:36 ` Scot Becker
2010-10-05 12:46 ` Sébastien Vauban
2010-10-05 14:17 ` Carsten Dominik
2010-10-05 14:30 ` Matthew Leifer
2010-10-05 15:02 ` Indraneel Majumdar
2010-10-05 16:26 ` Carsten Dominik
2010-10-05 18:55 ` Achim Gratz
2010-10-05 21:12 ` Carsten Dominik
2010-10-06 8:21 ` Sébastien Vauban
2010-10-05 18:24 ` Achim Gratz
2010-10-01 16:12 ` Nick Dokos
2010-10-06 9:36 ` Bruno Tavernier
2010-10-06 20:39 ` Matthew Leifer
2010-10-07 2:09 ` Bruno Tavernier
2010-10-13 7:49 ` Olivier Schwander
2010-10-13 12:34 ` Carsten Dominik
2010-10-06 21:54 ` Scot Becker
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=30671.1285861145@gamaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.com \
/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).