On Tue, 4 Nov 2008 13:13:58 +0100 Peter Dyballa <[EMAIL PROTECTED]> wrote:
PD> Am 04.11.2008 um 10:57 schrieb Ted Zlatanov:
>> OK, I'll run it that way and see how it goes. Why not put ns-
>> grabenv in the default init for everyone?
PD> Because it's usually not necessary. It's easy to synchronise the
PD> environment variables in a shell environment with those in a Mac OS X
PD> process environment, which to create no shell is necessary and
PD> therefore one needs ~/.MacOSX/environment.plist. Once this file is
PD> set up as the single point of failure you can easily re-use its
PD> contents and override settings coming some default places as in:
PD> .tcshrc:setenv LANG `defaults read "${HOME}/.MacOSX/environment" LANG`
PD> .tcshrc:set path=(`defaults read ~/.MacOSX/environment PATH |
PD> tr ':' ' '`)
PD> .bashrc:export LANG=$(defaults read "${HOME}/.MacOSX/environment" LANG)
PD> .bashrc:export PATH=$(defaults read "${HOME}/.MacOSX/environment" PATH)
I don't see why tcsh and bash settings make ns-grabenv unnecessary,
sorry. Most people run Emacs.app from the app bundle, not from the
command line, right?
Ted
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Emacs-app-dev- mailing list
Emacs-app-dev-@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emacs-app-dev-
