From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: bug in new exporter Date: Tue, 11 Jun 2013 14:08:05 +0200 Message-ID: <87txl4onoa.fsf@gmail.com> References: <87d2s388l2.fsf@pank.eu> <87ip1vjdlg.fsf@pierrot.dokosmarshall.org> <874ndf7xkn.fsf@pank.eu> <87fvwyrjnr.fsf@pierrot.dokosmarshall.org> <87y5aq7sin.fsf@pank.eu> <877gi8n3q7.fsf@gmail.com> <87obbko739.fsf@pierrot.dokosmarshall.org> <87r4ggmdtk.fsf@pierrot.dokosmarshall.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33507) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UmNMn-0001aU-F0 for emacs-orgmode@gnu.org; Tue, 11 Jun 2013 08:08:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UmNMk-0003sO-W0 for emacs-orgmode@gnu.org; Tue, 11 Jun 2013 08:08:01 -0400 Received: from mail-wi0-x22d.google.com ([2a00:1450:400c:c05::22d]:64174) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UmNMk-0003sG-QL for emacs-orgmode@gnu.org; Tue, 11 Jun 2013 08:07:58 -0400 Received: by mail-wi0-f173.google.com with SMTP id hq4so1824567wib.12 for ; Tue, 11 Jun 2013 05:07:58 -0700 (PDT) In-Reply-To: <87r4ggmdtk.fsf@pierrot.dokosmarshall.org> (Nick Dokos's message of "Wed, 05 Jun 2013 17:45:43 -0400") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nick Dokos Cc: emacs-orgmode@gnu.org Nick Dokos writes: > Nick Dokos 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. I also use texi2dvi, but I don't have any compilation problem with images, even with a relative path. Would you mind providing an ECM for that? Regards, -- Nicolas Goaziou