From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Hendy Subject: Re: minimal testing setup for pdf export? Date: Thu, 29 Aug 2019 10:27:24 -0500 Message-ID: References: <20190827081403.03c7b07b@lt70.mpip-mainz.mpg.de> <8fc0dad7-f387-0d81-7196-259f328f7f19@gmx.de> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:54902) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i3MKo-0004Fw-GM for emacs-orgmode@gnu.org; Thu, 29 Aug 2019 11:27:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i3MKm-0004Vl-U3 for emacs-orgmode@gnu.org; Thu, 29 Aug 2019 11:27:38 -0400 Received: from mail-qt1-x842.google.com ([2607:f8b0:4864:20::842]:35403) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1i3MKm-0004VF-Mb for emacs-orgmode@gnu.org; Thu, 29 Aug 2019 11:27:36 -0400 Received: by mail-qt1-x842.google.com with SMTP id u34so4128362qte.2 for ; Thu, 29 Aug 2019 08:27:36 -0700 (PDT) In-Reply-To: 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" To: Matt Price Cc: Julius Dittmar , org-mode-email , John Kitchin On Tue, Aug 27, 2019 at 6:34 PM Matt Price wrote: > > > > On Tue, Aug 27, 2019 at 1:33 PM John Kitchin wr= ote: >> >> that does suggest that pdflatex is getting called somewhere else. >> >> Maybe you can edebug the export function and check the value of default-= directory to see where it is getting called. >> >> You could also try this >> >> #+BEGIN_SRC emacs-lisp >> (defun my-build (quoted-tex-file) >> (message "Building %s. Called from %s" quoted-tex-file default-directo= ry)) >> >> (setq org-latex-pdf-process 'my-build) >> #+END_SRC >> >> It won't build the pdf, but it will tell you in the messages where it wa= s called from. It might help figure out what is happening. > > > huh. that was kinda cool... but the value of default-directory seems to = be correct. However, this helped a bit: > > #+BEGIN_SRC emacs-lisp > (shell-command-to-string "echo $PWD") > > #+END_SRC > > > #+RESULTS: > : /home/matt/src/org-mode > > Not sure what's going on here, but this value is the same in a regular em= acs and "emacs -Q". is this normal? > Did this get solved? It kind of bothers me to think it hasn't. I also think this is a case where erring on the side of overwhelming details would help a lot. Could you start from the beginning with the exact process using emacs -Q, post the full output of *Messages* and *Org PDF LaTeX Output*? Like in the above, you post the output of $PWD, but not what the *Messages* buffer contained from John's code. Maybe they are the same, maybe they are different, but we can't tell. Example: $ cd ~/ $ emacs -Q M-x org-version Org mode version 9.1.9 (release_9.1.9-65-g5e4542 @ /usr/share/emacs/26.2/lisp/org/) C-x C-f pdf-test.org File contents: * foo C-x C-s C-c C-e l p $ ls ~/ pdf-test.org pdf-test.pdf pdf-test.tex Alternatively, insert the code from John Kitchin: Wrote /home/jwhendy/pdf-text.org org-babel-exp process emacs-lisp at position 8... Saving file /home/jwhendy/pdf-text.tex... Wrote /home/jwhendy/pdf-text.tex Processing LaTeX file pdf-text.tex... Building pdf-text.tex. Called from /home/jwhendy/ org-compile-file: File "/home/jwhendy/pdf-text.pdf" wasn=E2=80=99t produced= . See "*Org PDF LaTeX Output*" for details I still don't feel I understand the full nature of your working directory, what does and doesn't get saved in that directory, etc. I'd love to help, but am not able to replicate for you! Thanks, John > >> John >> >> ----------------------------------- >> Professor John Kitchin >> Doherty Hall A207F >> Department of Chemical Engineering >> Carnegie Mellon University >> Pittsburgh, PA 15213 >> 412-268-7803 >> @johnkitchin >> http://kitchingroup.cheme.cmu.edu >> >> >> >> On Tue, Aug 27, 2019 at 8:57 AM Matt Price wrote: >>> >>> >>> >>> On Tue, Aug 27, 2019 at 8:27 AM John Kitchin = wrote: >>>> >>>> Can you manually compile the empty.tex file from the command line? eg >>>> >>>> pdflatex empty >>>> >>> (reposting to group) >>> >>> pdflatex empty >>> >>> Seems to work fine. Hmmm... >>>> >>>> John >>>> >>>> ----------------------------------- >>>> Professor John Kitchin >>>> Doherty Hall A207F >>>> Department of Chemical Engineering >>>> Carnegie Mellon University >>>> Pittsburgh, PA 15213 >>>> 412-268-7803 >>>> @johnkitchin >>>> http://kitchingroup.cheme.cmu.edu >>>> >>>> >>>> >>>> On Tue, Aug 27, 2019 at 7:57 AM Julius Dittmar = wrote: >>>>> >>>>> Am 27.08.19 um 12:34 schrieb Matt Price: >>>>> > This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019/Arch >>>>> > Linux) (preloaded format=3Dpdflatex) >>>>> > restricted \write18 enabled. >>>>> > entering extended mode >>>>> > ! I can't find file `empty.tex'. >>>>> >>>>> So pdflatex is called and found. Then pdflatex can't find empty.tex. >>>>> That looks like pdflatex is called in another directory than where >>>>> empty.tex resides. How that could happen, no idea. >>>>> >>>>> Julius >>>>>