From: "Charles C. Berry" <ccberry@ucsd.edu>
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: pdflatex not found?
Date: Tue, 27 Oct 2015 09:07:43 -0700 [thread overview]
Message-ID: <alpine.OSX.2.20.1510270856160.748@charles-berrys-macbook.local> (raw)
In-Reply-To: <87io5t6ubr.fsf@alphaville.usersys.redhat.com>
On Mon, 26 Oct 2015, Nick Dokos wrote:
> Peter Davis <pfd@pfdstudio.com> writes:
>
>> Nick Dokos <ndokos@gmail.com> writes:
>>
>>
>>> Peter Davis <pfd@pfdstudio.com> writes:
>>>
>>>> I'm trying to export PDF from org, but I'm getting the error:
>>>>
>>>> pdflatex: Command not found. [3 times]
>>>>
>>>> I've checked the definition of exec-path, and it includes
>>>> "/usr/texbin", which is where tcsh tells me the executable is.
>>>>
>>>> Any ideas?
>>>>
>>>
>>> Backtrace?
>>
>> Sorry. Here's the backtrace:
>>
>> Debugger entered--Lisp error: (error "PDF file ./test.pdf wasn't produced")
>> signal(error ("PDF file ./test.pdf wasn't produced"))
>> error("PDF file ./test.pdf wasn't produced")
>> org-latex-compile("./test.tex")
>> #[(file) "\301\b!\207" [file org-latex-compile] 2]("./test.tex")
>> org-export-to-file(latex "./test.tex" nil nil nil nil nil #[(file)
>> "\301\b!\207" [file org-latex-compile] 2])
>> org-latex-export-to-pdf(nil nil nil nil)
>> (org-open-file (org-latex-export-to-pdf nil s v b))
>> (if a (org-latex-export-to-pdf t s v b) (org-open-file (org-latex-export-to-pdf nil s v b)))
>> (lambda (a s v b) (if a (org-latex-export-to-pdf t s v b)
>> (org-open-file (org-latex-export-to-pdf nil s v b))))(nil nil nil nil)
>> org-export-dispatch(nil)
>> call-interactively(org-export-dispatch nil nil)
>> command-execute(org-export-dispatch)
>>
>> This seems less useful to me than the *Messages* buffer:
>>
>
> Yes, probably, but if I can get people to submit backtraces when getting
> an error, we can cut down the email volume by a factor of 2.43 (making up
> fictitious data to bolster my case...) In all seriousness, at least it
> shows that you are not going down some strange path.
>
> It's not clear to me why the error message in the message file is different
> from the error message above though.
>
>> Debug on Error enabled globally
>> org-babel-exp processing...
>> executing Dot code block...
>> Wrote /var/folders/d4/xb7t0gbd0f97p6494kz5xzdnmlncz8/T/babel-2213VOW/ob-input-22136yU
>> Code block evaluation complete.
>> Saving file /Users/davisp/Dropbox/HMH/test.tex...
>> Wrote /Users/davisp/Dropbox/HMH/test.tex
>> Processing LaTeX file ./test.tex...
>> pdflatex: Command not found. [3 times]
>> Entering debugger...
>> Mark set
>> End of buffer
>>
>> I did verify that the shell, my default of tcsh, does show pdflatex at
>> the right location, /usr/texbin/pdflatex
>>
>
> In combination, this pretty much says that org-latex-pdf-process was
> called (by examining the code for org-latex-compile) and it is set to
> the default value of invoking pdflatex three times (hence - probably -
> the "command not found 3 times" error), so as I said the standard path.
>
> As others have pointed out, your emacs does not know where to find
> pdflatex, even though your tcsh might. If your emacs is started from a
> tcsh that can find pdflatex, that would be strange; if it is started
> from your desktop environment/window manager, not so much (there are
> many things that could go wrong).
>
> OTOH, if exec-path contains the directory where pdflatex resides, then
> things are a bit screwy: exec-path is used by call-process, which is
> used by shell-command, which is used by org-latex-compile: so pdflatex
> should be found - that's a bit of a mystery.
shell-command (and call-process, I guess) seems not to use exec-path -
at least not always.
For example:
#+BEGIN_SRC emacs-lisp :results output
(shell-command "which ebrowse")
#+END_SRC
fails to find ebrowse even though exec-path leads to it.
And
#+BEGIN_SRC emacs-lisp
(shell-command "echo $PATH" "*path*")
#+END_SRC
shows what (getenv "PATH") yields - not exec-path
Give `setenv' a try.
Best,
Chuck
>
> What happens if you say M-x shell-command RET pdflatex RET?
>
> Somebody suggested running "which pdflatex" in your shell - what does
> that say?
>
> And you say it should be in /usr/texbin - what happens if you invoke
> it with an absolute path: "/usr/texbin/pdflatex" in your shell?
>
> --
> Nick
>
>
>
>
next prev parent reply other threads:[~2015-10-27 16:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 22:18 pdflatex not found? Peter Davis
2015-10-27 0:14 ` Nick Dokos
2015-10-27 5:45 ` Rainer M Krug
2015-10-27 16:07 ` Charles C. Berry [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-10-27 16:12 Peter Davis
2015-10-27 16:40 ` Rainer M Krug
2015-10-27 13:43 Peter Davis
2015-10-27 13:55 ` Fatma Başak Aydemir
2015-10-27 15:37 ` Nick Dokos
2015-10-27 15:48 ` Rainer M Krug
2015-10-27 15:51 ` John Kitchin
2015-10-27 15:58 ` Rainer M Krug
2015-10-27 16:06 ` Cook, Malcolm
2015-10-28 12:40 ` Alan Schmitt
2015-10-27 15:44 ` Rainer M Krug
2015-10-27 16:19 ` Nick Dokos
2015-10-27 16:45 ` Rainer M Krug
2015-10-27 17:02 ` Peter Davis
2015-10-27 17:50 ` Nick Dokos
2015-10-27 17:59 ` Peter Davis
2015-10-27 18:30 ` Rainer M Krug
2015-10-27 17:14 ` Nick Dokos
2015-10-27 15:40 ` Rainer M Krug
2015-10-26 19:26 Peter Davis
2015-10-26 19:50 ` John Hendy
2015-10-26 20:29 ` Myles English
2015-10-26 21:43 ` Charles C. Berry
2015-10-26 20:03 ` Nick Dokos
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=alpine.OSX.2.20.1510270856160.748@charles-berrys-macbook.local \
--to=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=ndokos@gmail.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).