From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: customising org-latex-to-pdf-process for bibtex
Date: Fri, 25 Feb 2011 18:10:03 -0800 [thread overview]
Message-ID: <20110225181003.35eab1c7@bhishma.homelinux.net> (raw)
In-Reply-To: <4DCBF55A-B3B5-4268-9456-3F2F7651581D@tsdye.com>
Hey Thomas,
Thanks for your response. I have outlined what I tried and found below.
On Fri, 25 Feb 2011 14:08:31 -1000
"Thomas S. Dye" <tsd@tsdye.com> wrote:
> Aloha Suvayu,
>
> I had what sounds like a similar problem. You don't say why bibtex
> fails, but in my case it wasn't able to find the .aux file. When I
> do this:
>
> (setq org-export-pdf-remove-logfiles nil)
>
> then I'm able to run bibtex without problems.
>
I tried that after your post, didn't seem to make a difference. I don't
know how to find how bibtex fails. All I see are these lines in the
"*Org PDF LaTeX Output*" buffer:
> No file msthesis.bbl.
> [5] (/home/jallad/org/masters-thesis//msthesis.aux)
>
> LaTeX Warning: There were undefined references.
Does that say anything to you? How do I capture the output from bibtex?
I presumed it is being overwritten by subsequent pdflatex runs. So I
removed the later pdflatex runs from the variable and that gives me
this output in the "*Org PDF LaTeX Output*" buffer.
> bibtex: Not writing to /home/user/org/masters-thesis/msthesis.blg
> (openout_any = p). I couldn't open file name
> `/home/user/org/masters-thesis/msthesis.blg'
However with the same tex file, after I run "bibtex msthesis" from the
terminal everything is fine! I even tried specifying the %b.aux in the
org-latex-to-pdf-process variable with no luck.
> I haven't tested your org-latex-to-pdf-process setups, so can't say
> whether or not there is a problem with them.
I use the TeXLive distributed by CTAN in isos. I setup my path so it
finds the right binaries whenever I'm working with latex. I am sure my
setup is fine as things are as expected when run from the teminal.
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2011-02-26 2:10 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 [this message]
[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
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=20110225181003.35eab1c7@bhishma.homelinux.net \
--to=fatkasuvayu+linux@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.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).