From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: pdflatex not found?
Date: Tue, 27 Oct 2015 11:37:05 -0400 [thread overview]
Message-ID: <871tcg7272.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: 562F826B.1080802@gmail.com
Fatma Başak Aydemir <aydemirfb@gmail.com> writes:
> I do not know the reasons but I had the same problem in the past on OS X.
>
> exec-path-from-shell package is a nice solution for that.
>
> https://github.com/purcell/exec-path-from-shell
>
Just the need for a package like that indicates that something is badly
broken on OS X, I think. To be fair, it's a mess on Linux as well, but
it is possible to make sure that variables you define (and export) in
your .profile get propagated to applications started by the DE/WM. In my
current installation (Fedora 21), that is done by
/etc/X11/xinit/xinitrc-common, which does this:
[ -r $HOME/.profile ] && . $HOME/.profile
Maybe OS X has a "hidden" mechanism like this?
> 27/10/15 14:43 tarihinde Peter Davis yazdı:
>> Rainer M Krug <r.m.krug@gmail.com> writes:
>>
>>> Envoyé de mon iPhone
>>>
>>>> Le 27 oct. 2015 à 01:14, Nick Dokos <ndokos@gmail.com> a écrit :
>>>>
>>>> Peter Davis <pfd@pfdstudio.com> writes:
>>>>
>>>>> Nick Dokos <ndokos@gmail.com> writes:
>>>> ...
>>>> 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.
>> I think the actual number is more like 2.17, but let's not quibble.
>>
>>>> What happens if you say M-x shell-command RET pdflatex RET?
>> Not found.
>>
>>>> Somebody suggested running "which pdflatex" in your shell - what does
>>>> that say?
>> Still not found. However, adding it to ~/.tcshrc seems to fix the
>> problem. That makes sense, but leaves two questions:
>>
>> 1) Why am I able to run pdflatex (without specifying the path) just
>> from the shell running in a terminal window?
>>
>> 2) What's the point of defining the emacs exec-path, since I needed
>> to define the shell's PATH variable anyway?
>>
FWIW, I never define exec-path explicitly: it is set from my $PATH when
emacs starts.
--
Nick
next prev parent reply other threads:[~2015-10-27 15:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 13:43 pdflatex not found? Peter Davis
2015-10-27 13:55 ` Fatma Başak Aydemir
2015-10-27 15:37 ` Nick Dokos [this message]
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
-- 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-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-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=871tcg7272.fsf@alphaville.usersys.redhat.com \
--to=ndokos@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).