From: "Charles C. Berry" <ccberry@ucsd.edu>
To: Myles English <mylesenglish@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: pdflatex not found?
Date: Mon, 26 Oct 2015 14:43:40 -0700 [thread overview]
Message-ID: <alpine.OSX.2.20.1510261440080.856@55.52.110.137.dynamic.ucsd.edu> (raw)
In-Reply-To: <87lhapbcg8.fsf@gmail.com>
On Mon, 26 Oct 2015, Myles English wrote:
>
>
> John Hendy writes:
>
>> On Mon, Oct 26, 2015 at 2:26 PM, Peter Davis <pfd@pfdstudio.com> wrote:
>>>
>>> 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.
>>
>> Someone else might have a better answer, but can you check your system
>> itself first? I'm guessing "exec-path" is an Org/Emacs variable?
>>
>> Just try:
>>
>> $ which pdflatex
>>
>> Or
>>
>> $ pdflatex --version
>>
>> That would be my suggestion for starters. At least then you know it's
>> definitely not your system/setup (my bet is that it is, though).
>>
>>
>> John
>>
>>>
>>> Any ideas?
>>>
>>> Thank you!
>>>
>>> -pd
>
> pd,
>
> After trying what has alreaddy been suggested you might try putting your
> cursor after the last bracket of this and pressing C-x C-e to see what
> emacs thinks your shell PATH environment variable is set to:
>
> (getenv "PATH")
>
> If you can't see the correct path in there then it should probably be
> set in ~/.profile or equivalent for tcsh rather than in ~/.tcshrc (I
> don't use tcsh so I just guessed that filename).
>
Or put something like
#+BEGIN_SRC emacs-lisp
(setenv "PATH"
"/usr/bin:/bin:/usr/sbin:/sbin:/usr/texbin:/usr/local/bin")
#+END_SRC
in your init file.
HTH,
Chuck
next prev parent reply other threads:[~2015-10-26 21:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 19:26 pdflatex not found? Peter Davis
2015-10-26 19:50 ` John Hendy
2015-10-26 20:29 ` Myles English
2015-10-26 21:43 ` Charles C. Berry [this message]
2015-10-26 20:03 ` Nick Dokos
-- strict thread matches above, loose matches on Subject: below --
2015-10-26 22:18 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
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-27 16:12 Peter Davis
2015-10-27 16:40 ` Rainer M Krug
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.1510261440080.856@55.52.110.137.dynamic.ucsd.edu \
--to=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=mylesenglish@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).