From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: Org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: customising org-latex-to-pdf-process for bibtex
Date: Tue, 1 Mar 2011 13:32:50 -0800 [thread overview]
Message-ID: <20110301133250.06f3436a@kuru.homelinux.net> (raw)
In-Reply-To: <87sjv6wp3j.fsf@ucl.ac.uk>
Hi Eric,
On Tue, 01 Mar 2011 20:41:20 +0000
Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
> Ah, very interesting. What I don't understand is why this is
> affecting you. I can see it affecting you if the aux file cannot be
> found but not if the first pdflatex step worked okay. Do you still
> have the problem if the first step worked?
>
Before the first pdflatex run the working directory seems correct:
> Invoked in dir /home/jallad/org/masters-thesis
In the output for this run I see some lines like these:
> [6]
> No file msthesis.bbl.
> [7] (./msthesis.aux)
I guess that means the .aux files are created?
> If so, and if you still have the sh file I sent to the list yesterday,
> can you add the following line to the top:
>
> echo 'Invoked in dir ' $PWD
>
> and post the output (the first few lines only) of the export to PDF
> when you get the error with bibtex?
Despite the above, for bibtex I get the following:
> --------------------------------- running bibtex next
>
> Invoked in dir /home/jallad/org/masters-thesis
>
> bibtex: Not writing to /home/jallad/org/masters-thesis/msthesis.blg
> (openout_any = p). I couldn't open file name
> `/home/jallad/org/masters-thesis/msthesis.blg'
Explicitly calling the texlive 2007 bibtex resolves the problem.
As per one of Tom's suggestions earlier in the thread, if I set
(setq org-export-pdf-remove-logfiles nil)
I can see the .aux files present after the final pdflatex run. Not
sure why bibtex overlooks that since the working directory seems
correct.
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2011-03-01 21:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 23:30 customising org-latex-to-pdf-process for bibtex suvayu ali
2011-02-26 0:23 ` Eric S Fraga
2011-02-26 2:18 ` Suvayu Ali
2011-02-28 9:23 ` Eric S Fraga
[not found] ` <4DCBF55A-B3B5-4268-9456-3F2F7651581D@tsdye.com>
2011-02-26 2:10 ` Suvayu Ali
[not found] ` <192D7D99-6918-424A-A047-6D6D1C1AF1DA@tsdye.com>
2011-02-26 2:48 ` Suvayu Ali
2011-02-28 16:06 ` Eric S Fraga
2011-02-28 20:45 ` Suvayu Ali
2011-02-28 20:51 ` Suvayu Ali
2011-03-01 8:54 ` Eric S Fraga
2011-03-01 4:31 ` Thomas S. Dye
2011-03-01 8:52 ` Eric S Fraga
2011-03-01 12:26 ` Suvayu Ali
2011-03-01 12:51 ` Eric S Fraga
2011-03-01 18:43 ` Suvayu Ali
2011-03-01 20:41 ` Eric S Fraga
2011-03-01 21:32 ` Suvayu Ali [this message]
2011-03-02 6:55 ` Eric S Fraga
2011-03-01 12:33 ` Carsten Dominik
2011-03-01 12:49 ` Eric S Fraga
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=20110301133250.06f3436a@kuru.homelinux.net \
--to=fatkasuvayu+linux@gmail.com \
--cc=e.fraga@ucl.ac.uk \
--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).