From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sanjib Sikder Subject: Re: Fwd: Citation in org mode does not compile Date: Wed, 3 Oct 2012 15:10:54 +0530 Message-ID: References: <12297.1349247878@alphaville> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=14dae9340f37d490aa04cb24712f Return-path: Received: from eggs.gnu.org ([208.118.235.92]:49251) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TJLSU-0006v9-0d for emacs-orgmode@gnu.org; Wed, 03 Oct 2012 05:41:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TJLSS-0003If-NO for emacs-orgmode@gnu.org; Wed, 03 Oct 2012 05:41:37 -0400 Received: from mail-ie0-f169.google.com ([209.85.223.169]:60882) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TJLSS-0003IZ-HV for emacs-orgmode@gnu.org; Wed, 03 Oct 2012 05:41:36 -0400 Received: by ied10 with SMTP id 10so19124680ied.0 for ; Wed, 03 Oct 2012 02:41:35 -0700 (PDT) In-Reply-To: <12297.1349247878@alphaville> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: nicholas.dokos@hp.com Cc: emacs-orgmode@gnu.org, "Thomas S. Dye" --14dae9340f37d490aa04cb24712f Content-Type: text/plain; charset=ISO-8859-1 Hi Dokos, I am sorry for the mistake, but what happened, in my original files, the references are all correct but when I thought of giving examples in the email, I did not put correct references. Anyways, thanks for your valuable input. ----------------------------- *Sanjib Sikder *Ph.D. Fellow Chemical Engineering IIT Bombay* * On Wed, Oct 3, 2012 at 12:34 PM, Nick Dokos wrote: > Sanjib Sikder 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 > previously). > > 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. > > Nick > > > --14dae9340f37d490aa04cb24712f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Dokos,

I am sorry for the mistake, but what happened, in my origi= nal files, the references are all correct but when I thought of giving exam= ples in the email, I did not put correct references.

Anyways, thanks= for your valuable input.

-----------------------------
Sanjib Sikder
Ph.D. Fellow
Chemical Engineering
IIT Bombay





On Wed, Oct 3, 2012 at 12:34 PM, Nick Do= kos <nicholas.dokos@hp.com> wrote:
Sanjib Sikder <sanjibju2002@gmail.com> wrote:

> HI,
>
> (setq org-latex-to-pdf-process '("texi2dvi --pdf --clean --ve= rbose --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 plac= e of refrences, I am getting questions
> marks.
>

I haven't gone through the whole thread, but I did go back and un= packed 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
previously).

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 a= n
org restriction.

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

Nick



--14dae9340f37d490aa04cb24712f--