emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: Sanjib Sikder <sanjibju2002@gmail.com>
Cc: emacs-orgmode@gnu.org, "Thomas S. Dye" <tsd@tsdye.com>
Subject: Re: Fwd: Citation in org mode does not compile
Date: Wed, 03 Oct 2012 03:04:38 -0400	[thread overview]
Message-ID: <12297.1349247878@alphaville> (raw)
In-Reply-To: Message from Sanjib Sikder <sanjibju2002@gmail.com> of "Thu, 27 Sep 2012 08:13:46 +0530." <CAL1SgUpPTywNvcxoZXzN7x+zdFkfh+YRCgFKZM9wwnRhDz84vQ@mail.gmail.com>

Sanjib Sikder <sanjibju2002@gmail.com> wrote:

> HI,
> (setq org-latex-to-pdf-process '("texi2dvi --pdf --clean --verbose --batch %f"))
> I have incorporated above line in my .emacs file. Now the C-c C-e p is not showing the error
> "Undefined citation" but the problem is still there. In place of refrences, I am getting questions
> marks.

I haven't gone through the whole thread, but I did go back and unpacked your files
from the original message. The problem there was indeed missing references:
your org file contains

| hi \citep{biswas2008generalized}
| hello \citep{cai1992length}

which did not match anything in the .bib file you attached to that
message. When I replaced them with the ones that *did* occur in your bib
file, like this:

--8<---------------cut here---------------start------------->8---
hi \citep{ashu1995molecular}
hello \citep{brush1967}
--8<---------------cut here---------------end--------------->8---

and I fixed a couple of things at the beginning of the file:

--8<---------------cut here---------------start------------->8---
# -*- mode: org -*-
#+TITLE: The Impact of Beer Consumption on Scientific Collaboration
--8<---------------cut here---------------end--------------->8---

everything worked fine (assuming that you added a call to bibtex
somewhere, either explicitly or by using texi2dvi, as indicated

The mode-setting line *has* to be on the first line: you can't leave
empty lines before it. The only exception is when the first line is a
shebang line, something like #! /bin/bash in a shell script: then the
mode-setting line has to be the second line. Emacs imposes this
restriction, not org.

There has to be a space after the # on that line: otherwise, it's not
interpreted as a comment and is included in the export output. That's an
org restriction.

Specifying the title is good practice, since otherwise the file name
becomes the title.


  parent reply	other threads:[~2012-10-03  7:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAL1SgUp87tichwJhr25VpnVTwniH+ivvoxoaiL_9oqFR-Ugcgg@mail.gmail.com>
2012-09-26 17:00 ` Sanjib Sikder
2012-09-26 18:38   ` Thomas S. Dye
2012-09-27  2:43     ` Sanjib Sikder
2012-09-27  3:14       ` Sanjib Sikder
2012-09-27  3:46         ` Yagnesh Raghava Yakkala
2012-09-27  3:59           ` Sanjib Sikder
2012-09-27  5:16             ` Yagnesh Raghava Yakkala
2012-09-27  5:28           ` Nick Dokos
2012-10-03  7:04       ` Nick Dokos [this message]
2012-10-03  9:40         ` Sanjib Sikder

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=12297.1349247878@alphaville \
    --to=nicholas.dokos@hp.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=sanjibju2002@gmail.com \
    --cc=tsd@tsdye.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).