emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-ref no bibliography generated in pdf
Date: Sun, 07 Feb 2016 21:57:34 -0500	[thread overview]
Message-ID: <87twljlxi9.fsf@pierrot.dokosmarshall.org> (raw)
In-Reply-To: CAN7vk5QmJV_j1Lb7wtZh7mtU+qk3pyUO+=NdaA4SrbDh4zgSAw@mail.gmail.com

Andreas Kiermeier <andreas.kiermeier@gmail.com> writes:

> On 7 February 2016 at 04:38, John Kitchin <jkitchin@andrew.cmu.edu> wrote:
>
>     that is why you don't get bibtex run then ;) try this
>     (setq org-latex-pdf-process
>            '("pdflatex -shell-escape -interaction nonstopmode -output-directory %o %b"
>              "bibtex %b"
>              "pdflatex -shell-escape -interaction nonstopmode -output-directory %o %b"
>              "pdflatex -shell-escape -interaction nonstopmode -output-directory %o %b"))
>
> ​Hi John & list,
>
> is there any reason why we should be hardcoding multiple runs of pdflatex​
>  
> ​(& bibtex) instead of using texify?
>
> I have my org-latex-to-pdf set to 
> "texify -p -b --tex-option=-shell-escape %f"​
> ​ (I'm on Windows 10, running MikTex 2.9), which hasn't given my any problems to date and
> seem to be a little more efficient​.
>

They are not hardcoded: that's just the default value of
org-latex-pdf-process which can be customized.

The three pdflatex runs are a "safe" default which avoids
incompatibilities between systems.

The customization options for org-latex-pdf-process list some other
possibilities which one might choose in preference to the default. If
texify can do the job (even if it does not exist on all systems of
interest), I would suggest adding it to the customizations menu of the
variable, so it can be chosen by a user as his/her personal default.

-- 
Nick

  parent reply	other threads:[~2016-02-08  2:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-06 13:42 org-ref no bibliography generated in pdf Nikolai Stenfors
2016-02-06 14:07 ` Eric S Fraga
2016-02-06 18:04   ` Nikolai
2016-02-06 18:08     ` John Kitchin
2016-02-06 18:49       ` Nikolai Stenfors
2016-02-07 23:21       ` Andreas Kiermeier
2016-02-08  0:03         ` John Kitchin
2016-02-08  2:57         ` Nick Dokos [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-02-06 15:19 John Kitchin
2016-02-06 17:16 ` Nikolai
2016-02-06 17:46   ` John Kitchin

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=87twljlxi9.fsf@pierrot.dokosmarshall.org \
    --to=ndokos@gmail.com \
    --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).