all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Reitter <david.reitter@gmail.com>
To: Francesco Lazzarino <flazzarino@gmail.com>,
	1555@emacsbugs.donarmstrong.com
Cc: bug-gnu-emacs@gnu.org
Subject: bug#1555: OSX Emacs.app not containing enough paths (emacs lisp fix included)
Date: Sat, 13 Dec 2008 14:42:31 -0500	[thread overview]
Message-ID: <121B2DBB-A5BA-4051-837B-F37C23A1EC9C@gmail.com> (raw)
In-Reply-To: <8574d28f0812121312q71d4c255wa849a4f0639d1925@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 751 bytes --]

On 12 Dec 2008, at 16:12, Francesco Lazzarino wrote:
>
> OSX seems to keep paths in /etc/paths and files in /etc/paths.d,  
> programs launched from Terminal seem to pick this up but Emacs.app  
> is not loaded from terminal so the path is kinda small.


Applications are not run from a login shell, so they don't inherit the  
same paths.  This is an old problem.
Your method of addressing this won't work with pre-10.5 versions of  
the OS.

The correct way is, IMHO, either leave it to the system to set the  
correct environment variables for the applications, or, as a  
convenience for users, start a login shell, print the environment and  
import it.  (I've been doing that in Aquamacs for a long time; the  
code is there if people want it.) 

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2193 bytes --]

  reply	other threads:[~2008-12-13 19:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2C9FF472-FCE0-4CCA-B84C-2505BC87F037@gmail.com>
2008-12-12 21:12 ` bug#1555: OSX Emacs.app not containing enough paths (emacs lisp fix included) Francesco Lazzarino
2008-12-13 19:42   ` David Reitter [this message]
2009-01-19 19:00   ` bug#1555: marked as done (OSX Emacs.app not containing enough paths (emacs lisp fix included)) Emacs bug Tracking System

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

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

  git send-email \
    --in-reply-to=121B2DBB-A5BA-4051-837B-F37C23A1EC9C@gmail.com \
    --to=david.reitter@gmail.com \
    --cc=1555@emacsbugs.donarmstrong.com \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=flazzarino@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.