Jeremy Huddleston wrote:
> > Is there a good way for me to pass my ENV to whatever is launched by
> > ~/.xinitrc.d/99-wm.sh, without passing the ENV to every single launchd
> > process?
>
> Yes.
>
> echo ". ~/.profile" > ~/.xinitrc.d/00-env.sh
> echo "cd $HOME" >> ~/.xinitrc.d/00-env.sh
> chm
On Mar 23, 2011, at 6:47 PM, Dave Ray wrote:
> Jeremy Huddleston wrote:
>
>>> I'm observing the same thing on shells that are launched by my window
>> manager (e17). Those shells are dropping me in at the root level, but my
>> ENV looks correct in those shells. $HOME=/Users/davidray. > >
>> Shel
Jeremy Huddleston wrote:
> > I'm observing the same thing on shells that are launched by my window
> manager (e17). Those shells are dropping me in at the root level, but my
> ENV looks correct in those shells. $HOME=/Users/davidray. > >
> Shells/terminals launched by X11.app (from the Application
On Mar 23, 2011, at 17:37, Dave Ray wrote:
> Peter Dyballa wrote:
>
>>> I'm not using bash, I'm true to tcsh. It works as described: What I
>>> set in ~/.login appears in the environment of the X clients. (The
>>> question stays: Why do I have to set the environment values twice?)
>>> And
On Mar 23, 2011, at 17:27, Dave Ray wrote:
> Peter Dyballa wrote:
>
>> The final release has a strange habit: it launches an extra xterm! How
>> can I stop it doing so?...
>
> I'm not sure if this is related to your extra xterm. I noticed in 2.6.1_final
> seems to reset my plist, it reverted
On Mar 23, 2011, at 14:24, Peter Dyballa wrote:
>
> Am 23.03.2011 um 19:44 schrieb Jeremy Huddleston:
>
>> As I mentioned earlier, it has to do with X11.app inheriting a login shell
>> environment from ~/.bash_profile, ~/.bash_login, or ~/.profile ... which
>> means it does not use ~/.bashrc.
On Mar 23, 2011, at 14:22, Dave Ray wrote:
> robert delius royar wrote:
>
>>> To reiterate, I am starting up X11 with only an xterm and no window
>>> manager. I am typing 'env' in that xterm. This where I'm seeing ENV
>>> being different from terminals opened normally. This is the only way I
Peter Dyballa wrote:
>> I'm not using bash, I'm true to tcsh. It works as described: What I
>> set in ~/.login appears in the environment of the X clients. (The
>> question stays: Why do I have to set the environment values twice?)
>> And X11.app obviously knows the value of $HOME; why doesn
Peter Dyballa wrote:
> > I'm not using bash, I'm true to tcsh. It works as described: What I
> > set in ~/.login appears in the environment of the X clients. (The
> > question stays: Why do I have to set the environment values twice?)
> > And X11.app obviously knows the value of $HOME; why d
Peter Dyballa wrote:
> The final release has a strange habit: it launches an extra xterm! How
> can I stop it doing so?...
I'm not sure if this is related to your extra xterm. I noticed in 2.6.1_final
seems to reset my plist, it reverted to the default which opens an xterm from
launchd. I fol
Am 19.03.2011 um 18:41 schrieb Jeremy Huddleston:
You might as well try the final release (2.6.1).
The final release has a strange habit: it launches an extra xterm! How
can I stop it doing so? I really don't need it, the *shell* buffer in
GNU Emacs is much better (and now even quite ANSI
Am 23.03.2011 um 19:44 schrieb Jeremy Huddleston:
As I mentioned earlier, it has to do with X11.app inheriting a login
shell environment from ~/.bash_profile, ~/.bash_login, or
~/.profile ... which means it does not use ~/.bashrc. Non-login
shells use ~/.bashrc. If you want your ~/.bashr
robert delius royar wrote:
>> To reiterate, I am starting up X11 with only an xterm and no window
>> manager. I am typing 'env' in that xterm. This where I'm seeing ENV
>> being different from terminals opened normally. This is the only way I
>> can capture the difference in what env is being p
Wed, 23 Mar 2011 (13:04 -0700 UTC) Dave Ray wrote:
To reiterate, I am starting up X11 with only an xterm and no window
manager. I am typing 'env' in that xterm. This where I'm seeing ENV
being different from terminals opened normally. This is the only way I
can capture the difference in what e
On Mar 23, 2011, at 11:44 AM, Jeremy Huddleston wrote:
> Did you miss my response to you? Or did you miss my response to him that his
> statement is actually incorrect.
I saw your post, but what you are describing is not consistent to what I'm
observing on my machine. It's not that I don't be
On Mar 23, 2011, at 10:02, Dave Ray wrote:
> On Mar 23, 2011, at 7:00 AM, Peter Dyballa wrote:
>
IMO this should not be necessary, because up to Leopard ~/.MacOSX/
environment.plist is read when you log in. Then all processes
inherit this environment. The X clients are a bit di
On Mar 23, 2011, at 7:00 AM, Peter Dyballa wrote:
>>> IMO this should not be necessary, because up to Leopard ~/.MacOSX/
>>> environment.plist is read when you log in. Then all processes
>>> inherit this environment. The X clients are a bit different and
>>> used to inherit their environment
Am 23.03.2011 um 00:48 schrieb Jeremy Huddleston:
Why do you find yourself needing ~/.MacOSX/environment at all?
It's so simple (elegant?) and it can be made the single point of
failure. Instead of constantly updating a dozen different files it's
better to update these files once to use t
18 matches
Mail list logo
