At a glance, exec-path should be $PATH + /Applications/Emacs.app/
Contents/MacOS/libexec + /Applications/Emacs.app/Contents/MacOS/bin +
(additions by site-start.el).
Your result seems to be strange.
Seiji
On 2008/06/01, at 12:50, Simon Wright wrote:
>
> The option to Support Typical Unix Paths (which took me a while to
> find!) appears not to update exec-path.
>
> (getenv "PATH") returns /usr/bin:/bin:/usr/sbin:/sbin:~/bin:/usr/
> local/bin:/usr/X11R6/bin
>
> C-h v exec-path returns ("/usr/local/bin" "/usr/bin" "/bin" "/usr/
> sbin" "/sbin" "/Applications/Emacs.app/Contents/MacOS/libexec" "/
> Applications/Emacs.app/Contents/MacOS/bin" "/usr/X11R6/bin")
>
> I have no TeX or related apps installed.
>
> What I don't understand is why PATH and exec-path are so different,
> given the call in site-start.el to carbon-emacs-package-add-to-path.
>
> I'm not sure if this has changed recently; I've only noticed it since
> moving to Leopard on Macbook Pro from Tiger on Powerbook.
>
> >
--~--~---------~--~----~------------~-------~--~----~
Carbon Emacs User Group
http://groups.google.com/group/carbon-emacs?hl=en
-~----------~----~----~----~------~----~------~--~---
