From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: "Young, Ed" <Ed_Young@cable.comcast.com>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: How to make emacs path aware on MacOSX
Date: Thu, 14 Apr 2011 16:18:04 +0200 [thread overview]
Message-ID: <1422A758-0334-4BD5-AC99-0E19E208C03B@Web.DE> (raw)
In-Reply-To: <C9CC4105.4087%ed_young@cable.comcast.com>
Am 14.04.2011 um 14:19 schrieb Young, Ed:
> Sorry, but that doesn't make any sense to me. If I define a variable
> in
> the environment.plist file,
I did not understand completely what you wrote and assumed that you
were still referring to the usual files a shell interpreter is reading
when it is started.
> and then log out and back in (that's a pain) the variables are
> available.
Mac OS X allows to set up some so-called "Startup Items"...
>
> The problem is when I try to embed a variable in the value of another
> variable:
>
> SW_HOME /opt/comcast/software
> GROOVY_HOME $SW_HOME/groovy/current
>
> In the case above, SW_HOME doesn't resolve correctly in the
> GROOVY_HOME
> variable.
That's indeed not possible inside ~/.MacOSX/environment.plist. It's
just a simple text, or, better: XML file. Inside it no substitution
happens. With GNU Emacs or some other editor it's really not that
complicated to substitute variable names with the contents they stand
for.
OTOH, a shell should be able resolve a setting like "$SW_HOME/groovy/
current" when "$SW_HOME" is given. Proof:
ls -l $SW_HOME/groovy/current
--
Greetings
Pete <]
o __o |__ o HPV, the real
___o /I -\<, |o \ -\),-% high speed!
___/\ /\___./ \___...O/ O____.....`-O-'-()--o_________________
prev parent reply other threads:[~2011-04-14 14:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 12:14 How to make emacs path aware on MacOSX Young, Ed
2011-04-13 20:53 ` Edward O'Connor
2011-04-13 20:58 ` Perry Smith
2011-04-13 23:00 ` Peter Dyballa
2011-04-14 2:17 ` Young, Ed
2011-04-14 9:05 ` Peter Dyballa
2011-04-14 12:19 ` Young, Ed
2011-04-14 14:18 ` Peter Dyballa [this message]
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=1422A758-0334-4BD5-AC99-0E19E208C03B@Web.DE \
--to=peter_dyballa@web.de \
--cc=Ed_Young@cable.comcast.com \
--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).