unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Josh <josh@foxtail.org>
To: Darren Hoo <darren.hoo@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: About PATH environment variable on OSX
Date: Fri, 12 Apr 2013 21:59:56 -0700	[thread overview]
Message-ID: <CANdFEAFYPPwMWbvjoX3HROsFEMX2O_6mZ3f70ZhpaHxPx+Sxjg@mail.gmail.com> (raw)
In-Reply-To: <m2ppy6td88.fsf@gmail.com>

Others have made good suggestions already, but I prefer the approach
shown at http://paste.lisp.org/display/132476 because with a few elisp
functions I can manage my environment variables in my shell profile as
usual with no need to bother with silly OSXisms.

On Sun, Apr 7, 2013 at 11:19 AM, Darren Hoo <darren.hoo@gmail.com> wrote:
>
> In the Emacs info manual F.1.1 Grabbing environment variables
> it says and I quote:
>
>       For the PATH and MANPATH variables, a system-wide method of setting
>    PATH is recommended on Mac OS X 10.5 and later, using the `/etc/paths'
>    files and the `/etc/paths.d' directory.
>
> It doesn't work for me. This is my /etc/paths file:
>
> $ cat /etc/paths
> /usr/bin
> /bin
> /usr/sbin
> /sbin
> /usr/local/bin
>
> but (getenv "PATH") gives "/usr/bin:/bin:/usr/sbin:/sbin"
> and I haven't used any (setenv "PATH" ...) in my init file.
>
> I can confirm that PATH settings in the /etc/paths and /etc/paths.d are
> never picked up by the programs launched from the Finder by writing a
> simple Cocoa App.
>
> I can not find any NS-specific code that read the /etc/paths file
> either.
>
> So I think the paragraph I quoted above in the manual is incorrect and
> should be removed.
>
>



  parent reply	other threads:[~2013-04-13  4:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-07 18:19 About PATH environment variable on OSX Darren Hoo
2013-04-12  5:05 ` Jan Djärv
2013-04-12 12:39   ` Piotr Kalinowski
2013-04-12 14:07     ` Peter Vasil
2013-04-13  1:24       ` James Felix Black
2013-04-13 12:33         ` Piotr Kalinowski
2013-04-12 15:01   ` Harald Hanche-Olsen
2013-04-13  4:59 ` Josh [this message]
2013-04-13 12:41   ` Piotr Kalinowski

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CANdFEAFYPPwMWbvjoX3HROsFEMX2O_6mZ3f70ZhpaHxPx+Sxjg@mail.gmail.com \
    --to=josh@foxtail.org \
    --cc=darren.hoo@gmail.com \
    --cc=emacs-devel@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.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).