emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Mikhail Titov" <mlt@gmx.us>
To: 'Eric Fraga' <e.fraga@ucl.ac.uk>, "'Alan E. Davis'" <lngndvs@gmail.com>
Cc: 'Julian Burgos' <julian@hafro.is>, emacs-orgmode@gnu.org
Subject: Re: problems with LaTex/BibTex
Date: Wed, 25 Apr 2012 10:59:14 -0500	[thread overview]
Message-ID: <002d01cd22fc$5e18f7d0$1a4ae770$@us> (raw)
In-Reply-To: <87k414kqg2.fsf@ucl.ac.uk>

> -----Original Message-----
> From: emacs-orgmode-bounces+mlt=gmx.us@gnu.org [mailto:emacs-orgmode-
> bounces+mlt=gmx.us@gnu.org] On Behalf Of Eric Fraga
> Sent: Wednesday, April 25, 2012 6:21 AM
> To: Alan E. Davis
> Cc: Julian Burgos; emacs-orgmode@gnu.org
> Subject: Re: [O] problems with LaTex/BibTex
> "Alan E. Davis" <lngndvs@gmail.com> writes:
> > I would have a use for this.  I am curious, though...
> >
> > Suppose I use this as a standard init-file declaration for
> > org-latex-to-pdf-process .  Does that mean that bibtex will always be
> > every time, during the generation of PDFs via LaTex export?
> Yes but you can easily customise this variable on a per file basis.  If
> you seldom use bibtex, have the default be to run pdflatex just
> once.  Then, for any org file that needs bibtex, simply put in the
> following line (or a variation thereof):
> #+BIND: org-latex-to-pdf-process ("pdflatex %b" "bibtex %b" "pdflatex %b"
> "pdflatex %b")

Also, if you are on Windows with MikTeX, you can use texify, otherwise
latexmk can save you some time when it is not necessary to rebuild index
and/or bibliography.


      reply	other threads:[~2012-04-25 15:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-30  1:41 problems with LaTex/BibTex Julian Burgos
2012-03-30  8:05 ` suvayu ali
2012-03-30 11:54   ` Julian Burgos
2012-03-31  1:15     ` Alan E. Davis
2012-03-31  4:20       ` Nick Dokos
2012-04-25 11:21       ` Eric Fraga
2012-04-25 15:59         ` Mikhail Titov [this message]

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:

  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='002d01cd22fc$5e18f7d0$1a4ae770$@us' \
    --to=mlt@gmx.us \
    --cc=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=julian@hafro.is \
    --cc=lngndvs@gmail.com \


* 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


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).