unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Lars Wessman <lars.wessman@gmail.com>
To: Peter Dyballa <Peter_Dyballa@Web.DE>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Cocoa Emacs 23 and Tramp problem
Date: Sat, 7 Mar 2009 10:36:22 +0000	[thread overview]
Message-ID: <54BB6DFE-36A2-4111-AE31-440D9E2C4F93@gmail.com> (raw)
In-Reply-To: <0B559F6A-06E7-46A6-A927-2AE77104989D@Web.DE>


On Mar 7, 2009, at 12:24 AM, Peter Dyballa wrote:

>
> Am 07.03.2009 um 00:59 schrieb Lars Wessman:
>
>> I'll try this out tomorrow, and then maybe I'll look to see if this  
>> info is in the emacs wiki and, if not, add it in an appropriate  
>> place.
>
>
> If you do so, you could also mention that with ~/.MacOSX/ 
> environment.plist you have one "single point of failure:" you don't  
> need to mess with PATH or path settings in different (login) shell  
> RC files. Whenever you need a particular environment variable  
> globally, you can put it there. Since the process environment does  
> not automatically change when ~/.MacOSX/environment.plist is  
> changed, and it could happen that you log in to your or some other  
> Mac from remote, you can also use ~/.MacOSX/environment.plist as the  
> single source for quite up-to-date environment settings in shell by  
> using in ~/.bashrc or such:
>
> 	export PATH=$(defaults read "${HOME}/.MacOSX/environment" PATH)
>
> or in ~/.(t)cshrc or such:
>
> 	set path=(`defaults read ~/.MacOSX/environment PATH | tr ':' ' '`)
>
> I.e.: instead of editing half a dozen files every time you care for  
> just a single one.
>
> --
> Greetings
>
>  Pete
>
> I love deadlines. I love the whooshing noise they make as they go by.
> 				– Douglas Adams

I just checked this out. It seems that my ~/.macosx/environment.plist  
has been there with the PATH variable in it all the time. For some  
reason it is not being picked up. I tested this again by commenting  
out the code I got from Aquamacs, and the contents of the  
environment.plist file was not being loaded again. I seems that this  
is problem.

After some googling, I cross a little package ( http://edward.oconnor.cx/elisp/osx-plist.el 
  ) for parsing plists that also happens to have the code for loading  
~/.macosx/environment.plist as sample code. I just tested it and it  
works like a charm.

So there are two choices, the code I took from Aquamacs, or osx- 
plist.el. osx-plist.el is probably the preferred method, since .emacs  
loads twice as fast using osx-plist.el than it does when using the  
Aquamacs code. This is likely due to the fact that the process of  
lifting the data directly from the shell is a bit slow, as Dave  
Reitter says in the comments to the code.

Cheers

Lars



  reply	other threads:[~2009-03-07 10:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-06 18:35 Cocoa Emacs 23 and Tramp problem Lars Wessman
2009-03-06 20:46 ` dericbytes
2009-03-06 21:08   ` Lars Wessman
2009-03-06 22:15     ` Ted Zlatanov
2009-03-06 22:57       ` Lars Wessman
2009-03-06 22:58       ` Lars Wessman
2009-03-06 23:17 ` Peter Dyballa
2009-03-06 23:59   ` Lars Wessman
2009-03-07  0:24     ` Peter Dyballa
2009-03-07 10:36       ` Lars Wessman [this message]
2009-03-07 12:17         ` Peter Dyballa
2009-03-07 14:14           ` Lars Wessman
2009-03-07 16:01             ` Peter Dyballa
2009-03-07 17:30               ` Lars Wessman

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=54BB6DFE-36A2-4111-AE31-440D9E2C4F93@gmail.com \
    --to=lars.wessman@gmail.com \
    --cc=Peter_Dyballa@Web.DE \
    --cc=help-gnu-emacs@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.
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).