From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: bug in new exporter Date: Wed, 05 Jun 2013 17:45:43 -0400 Message-ID: <87r4ggmdtk.fsf@pierrot.dokosmarshall.org> 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> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:35668) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UkLWp-00046H-Id for emacs-orgmode@gnu.org; Wed, 05 Jun 2013 17:46:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UkLWl-00006N-2Q for emacs-orgmode@gnu.org; Wed, 05 Jun 2013 17:45:59 -0400 Received: from plane.gmane.org ([80.91.229.3]:42797) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UkLWk-00006E-N9 for emacs-orgmode@gnu.org; Wed, 05 Jun 2013 17:45:54 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1UkLWj-0002bp-Pm for emacs-orgmode@gnu.org; Wed, 05 Jun 2013 23:45:53 +0200 Received: from pool-108-7-96-134.bstnma.fios.verizon.net ([108.7.96.134]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 05 Jun 2013 23:45:53 +0200 Received: from ndokos by pool-108-7-96-134.bstnma.fios.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 05 Jun 2013 23:45:53 +0200 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: emacs-orgmode@gnu.org 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. -- Nick