From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Nikolai <nikolai.stenfors@gapps.umu.se>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: org-ref no bibliography generated in pdf
Date: Sat, 6 Feb 2016 12:46:57 -0500 [thread overview]
Message-ID: <CAJ51ETrARJdQG25O9gU_ekF+vGCoqE9JDoY=JxVkGqZN9C4uMA@mail.gmail.com> (raw)
In-Reply-To: <loom.20160206T181132-705@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 879 bytes --]
Then Eric is probably right:what is org-latex-to-pdf-process set to?
John
-----------------------------------
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
On Sat, Feb 6, 2016 at 12:16 PM, Nikolai <nikolai.stenfors@gapps.umu.se>
wrote:
> John Kitchin <johnrkitchin <at> gmail.com> writes:
>
> >
> > It could also be you didn't specify a bibliographystyle.
> >
> > Try running M-x org-ref on the file. It checks that some things like that
> are correct. Sometimes it is
> > helpful to manually build the puff at the command line. Org hides a lot
> of
> errors sometimes.
> >
>
> Thank you Prof. Kitchen,
>
> Tried your suggestions with same result: references marked as [?] and no
> bibliography generated.
>
> /Nikolai
>
>
>
>
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 1711 bytes --]
next prev parent reply other threads:[~2016-02-06 17:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-06 15:19 org-ref no bibliography generated in pdf John Kitchin
2016-02-06 17:16 ` Nikolai
2016-02-06 17:46 ` John Kitchin [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-02-06 13:42 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
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='CAJ51ETrARJdQG25O9gU_ekF+vGCoqE9JDoY=JxVkGqZN9C4uMA@mail.gmail.com' \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@gnu.org \
--cc=nikolai.stenfors@gapps.umu.se \
/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).