Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Resolved: Sourcing .zshrc from .zprofile causes problems
- X-seq: zsh-users 7845
- From: Wayne Davison <wayned@xxxxxxxxxxxxxxxxxxxxx>
- To: zsh-users@xxxxxxxxxx
- Subject: Re: Resolved: Sourcing .zshrc from .zprofile causes problems
- Date: Sat, 14 Aug 2004 21:58:45 -0700
- In-reply-to: <20040814182036.GS7509@xxxxxxxxxxxxx>
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <7E0A2482-ECC4-11D8-A541-000A95D2C79E@xxxxxxxxxxxxxxxx> <Pine.LNX.4.61.0408122151280.15905@xxxxxxxxxxxxxxxxxx> <F692BDE6-EE06-11D8-BE5C-000A95D2C79E@xxxxxxxxxxxxxxxx> <20040814182036.GS7509@xxxxxxxxxxxxx>
On Sat, Aug 14, 2004 at 08:20:36PM +0200, Vincent Lefevre wrote:
> You should define LC_COLORS in your .zshenv file.
Not necessarily. The .zshenv file is for things that are needed by all
shells, including non-interactive scripts. As such, I would suggest
just exporting LC_COLORS from .zprofile and leaving it alone.
The only thing I have in my .zshenv script is this:
if [[ $SHLVL == 1 && ! -o LOGIN ]]; then
source ~/.zprofile
fi
This is a kludge that ensured that an xterm that didn't start with any
of my login settings sourced my .zprofile. I'm not sure if it's still
needed with a modern X Windows setup, though. Hmm, I wonder if that
works right with a cron-initiated zsh script? Perhaps not...
I used to set things like the PATH in the .zshenv file until it caused
me problems using gdb: gdb runs the executable using $SHELL, and that
caused some of my debug environment settings to get overridden (ouch).
..wayne..
Messages sorted by:
Reverse Date,
Date,
Thread,
Author