emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Noorul Islam K M <noorul@noorul.com>
To: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Compiling multiple times the LaTeX output
Date: Wed, 29 Sep 2010 20:47:56 +0530	[thread overview]
Message-ID: <87r5gcshnf.fsf@noorul.maa.corp.collab.net> (raw)
In-Reply-To: <87zkv0pqyi.fsf@mundaneum.com> ("Sébastien Vauban"'s message of "Wed, 29 Sep 2010 16:25:09 +0200")

Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> writes:

> Hello,
>
> I've been taught of a weird observation: the page number indicated in the TOC
> of a PDFLaTeX output is wrong by one page...
>
> I've re-exported my Org document. Same observation. So, it was not a problem
> during export or so.
>
> Taking the `.tex' file, and running `pdflatex' on it shows me twice this
> message:
>
> LaTeX Warning: Label(s) may have changed. Rerun to get cross-references right.
>
> After the 3rd compilation, everything is right in the PDF.
>
> Is it possible, somehow, that Org does not run `pdflatex' enough times??
>

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.  %f in the command will be replaced by the full file name,
%b
by the file base name (i.e. without extension) and %o by the base
directory
of the file.
The reason why this is a list is that it usually takes several runs of
pdflatex, maybe mixed with a call to bibtex.  Org does not have a clever
mechanism to detect which of these commands have to be run to get to a
stable
result, and it also does not do any error checking.

Alternatively, this may be a Lisp function that does the processing, so
you
could use this to apply the machinery of AUCTeX or the Emacs LaTeX mode.
This function should accept the file name as its single argument."

Thanks and Regards
Noorul

  reply	other threads:[~2010-09-29 15:31 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 [this message]
2010-09-30 13:27   ` [PATCH] " Sébastien Vauban
2010-09-30 15:39     ` Nick Dokos
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=87r5gcshnf.fsf@noorul.maa.corp.collab.net \
    --to=noorul@noorul.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).