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 10:43:34 -0800 [thread overview]
Message-ID: <20110301104334.63fe4eec@bhishma.homelinux.net> (raw)
In-Reply-To: <878vwzf1h1.fsf@pinto.chemeng.ucl.ac.uk>
Hi Eric and others,
On Tue, 01 Mar 2011 12:51:22 +0000
Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
> Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
>
> [...]
>
> > Although I get perfect results using the Fedora 13 provided texlive
> > (2007), I noticed I get that old error again (quoted below) when I
> > use the texlive 2010 install from CTAN. Maybe some problem in my
> > setup. I will use my distribution provided texlive for now.
> >
> > Thanks again for being so patient and helping with my issues. :)
> >
> >> 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'
>
> Sorry; this I cannot help with much as I'm not sure what is happening
> here and I've never run into this before.
>
> Are there any problems with that file (e.g. read only mode)? Is the
> file there? If so, what happens if you remove it? It should be
> created automatically by bibtex.
>
This happens with a clean working directory.
> 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
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2011-03-01 18: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 [this message]
2011-03-01 20:41 ` Eric S Fraga
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=20110301104334.63fe4eec@bhishma.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).