From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: bug in new exporter
Date: Wed, 05 Jun 2013 17:45:43 -0400 [thread overview]
Message-ID: <87r4ggmdtk.fsf@pierrot.dokosmarshall.org> (raw)
In-Reply-To: 87obbko739.fsf@pierrot.dokosmarshall.org
Nick Dokos <ndokos@gmail.com> writes:
> Just a heads-up: As part of testing this, I stumbled on an unrelated
> current-working-directory problem, where on exporting to pdf, the
> pdflatex of the produced tex file fails to find an image file specified
> with a relative pathname (it works fine with an absolute path name). The
> tex file looks OK and I can process it from the command line. I'll try
> to pin this down more precisely, but do I understand correctly that the
> processing of the tex file should take place with the current working
> directory set to the directory of the org file?
>
The problem was that I had customized my org-latex-pdf-process to the
texi2dvi recommended value:
texi2dvi -p -b -c -V %f
The -c (equivalently: --clean or --build=clean) breaks relative paths
because texi2dvi executes in a different directory. The *Org PDF LaTeX
Output* buffer shows
/usr/bin/texi2dvi: cd /home/nick/src/org/latex/foo.t2d/pdf/build
whereas the org file was in /home/nick/src/org/latex.
If you use texi2dvi, beware of -c (and also --tidy I presume).
So nothing to do with org, but maybe the customization option should not
include the -c.
--
Nick
next prev parent reply other threads:[~2013-06-05 21:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 15:50 bug in new exporter Marvin Doyley
2013-06-03 16:25 ` Rasmus
2013-06-03 17:42 ` Nick Dokos
2013-06-03 20:23 ` Rasmus
2013-06-03 21:03 ` Nick Dokos
2013-06-03 22:12 ` Rasmus
2013-06-05 12:26 ` Nicolas Goaziou
2013-06-05 16:28 ` Nick Dokos
2013-06-05 21:45 ` Nick Dokos [this message]
2013-06-11 12:08 ` Nicolas Goaziou
2013-06-11 17:09 ` Nick Dokos
2013-06-16 20:53 ` Nicolas Goaziou
2013-06-11 12:05 ` Nicolas Goaziou
-- strict thread matches above, loose matches on Subject: below --
2013-06-03 17:22 Marvin Doyley
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=87r4ggmdtk.fsf@pierrot.dokosmarshall.org \
--to=ndokos@gmail.com \
--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).