[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] Fwd: Citation in org mode does not compile

From: Nick Dokos
Subject: Re: [O] Fwd: Citation in org mode does not compile
Date: Wed, 03 Oct 2012 03:04:38 -0400

Sanjib Sikder <address@hidden> 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 
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.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]