From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Suvayu Ali <fatkasuvayu+linux@gmail.com>
Cc: Org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: customising org-latex-to-pdf-process for bibtex
Date: Tue, 01 Mar 2011 20:41:20 +0000 [thread overview]
Message-ID: <87sjv6wp3j.fsf@ucl.ac.uk> (raw)
In-Reply-To: <20110301104334.63fe4eec@bhishma.homelinux.net> (Suvayu Ali's message of "Tue, 1 Mar 2011 10:43:34 -0800")
Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
[...]
>> Have you tried searching the web with that error message (e.g. google
>> bibtex openout_any)?
>>
>
> I found a recent (Jan 2010) discussion about this. There was a change in
> behaviour for bibtex in the latest texlive build which leads to this
> behaviour. You can follow the discussion in this thread[1]. The TeX
> developers expect external tools like org and other editor plugins to
> adapt to this change. I think this is why I was having problems in the
> first place, not sure how this can be resolved though. If we find a
> solution it would be worth a mention on Worg.
>
> [1] http://web.archiveorange.com/archive/v/VBuN9l7WNXs4SXOn6Kxh
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?
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?
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.4 (release_7.4.576.g99675.dirty)
next prev parent reply other threads:[~2011-03-01 20:44 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 [this message]
2011-03-01 21:32 ` Suvayu Ali
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=87sjv6wp3j.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=fatkasuvayu+linux@gmail.com \
/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).