From: "Alan E. Davis" <email@example.com>
To: Julian Burgos <firstname.lastname@example.org>
Subject: Re: problems with LaTex/BibTex
Date: Fri, 30 Mar 2012 18:15:57 -0700 [thread overview]
Message-ID: <CAF-1L2TqSpt=yKo6-Hz0ffma1mJMsXdzBBfX3jt1E=CUKFQemail@example.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1559 bytes --]
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 run,
every time, during the generation of PDFs via LaTex export?
On Fri, Mar 30, 2012 at 4:54 AM, Julian Burgos <firstname.lastname@example.org> wrote:
> Yes! That was it. Thanks!!
> On fös 30.mar 2012 08:05, suvayu ali wrote:
>> Hey Julian,
>> On Fri, Mar 30, 2012 at 03:41, Julian Burgos<email@example.com> wrote:
>>> The "References.bib" is a BibTex file in the same folder as the test
>>> The citations were entered using RefTex with no problem. But when
>>> exporting to pdf, I get the following message in the minibuffer:
>>> "Exporting to PDF...done, with some errors: [undefined citations]". The
>>> pdf produced had, of course, question marks where the citations should
>> Did you customise your org-latex-to-pdf-process to include bibtex? I use
>> something like this:
>> (setq org-latex-to-pdf-process '("pdflatex -interaction nonstopmode %b"
>> "/usr/bin/bibtex %b"
>> "pdflatex -interaction nonstopmode %b"
>> "pdflatex -interaction nonstopmode %b"))
> Julian Mariano Burgos, PhD
> Hafrannsóknastofnunin/Marine Research Institute
> Skúlagata 4, 121 Reykjavík, Iceland
> Sími/Telephone : +354-5752037
> Bréfsími/Telefax: +354-5752001
> Netfang/Email: firstname.lastname@example.org
[-- Attachment #2: Type: text/html, Size: 2469 bytes --]
next prev parent reply other threads:[~2012-03-31 1:16 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 [this message]
2012-03-31 4:20 ` Nick Dokos
2012-04-25 11:21 ` Eric Fraga
2012-04-25 15:59 ` Mikhail Titov
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 \
* 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).