From: Wayne Davison <wayned@users.sourceforge.net>
To: Nikolai Weibull <lone-star@home.se>
Cc: zsh-users@sunsite.dk
Subject: Re: ~/.zshenv or ~/.zprofile
Date: Sun, 3 Aug 2003 15:39:49 -0700 [thread overview]
Message-ID: <20030803223949.GA18476@binome.blorf.net> (raw)
In-Reply-To: <20030803221858.GA2720@puritan.pcp.ath.cx>
On Mon, Aug 04, 2003 at 12:18:58AM +0200, Nikolai Weibull wrote:
> The problem really is that if you put, for example, your PATH
> definition in ~/.zshenv, and have a script or application that
> modifies PATH and later runs a shell, that shell will not use the
> specifically crafted PATH, but will read the standard one from
> ~/.zshenv.
Exactly. I got bit by this a few years ago when I had a .zshenv file
and was using gdb -- it runs a $SHELL to start the debugged program,
and this overrode some environment values that I did NOT want touched
(ouch). I now use no .zshenv file at all, and I cannot think of any
good reason for me (or for most typical users) to need one.
I now use .zprofile and .zshrc, and I even have a special line in my
.zshrc file that sources .zprofile if it discovers that .zprofile has
not been sourced yet (which had happened to me in some circumstances
before, but is not a problem in my current situation where I first
login, and then run X Windows).
..wayne..
next prev parent reply other threads:[~2003-08-03 22:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-03 22:18 Nikolai Weibull
2003-08-03 22:39 ` Wayne Davison [this message]
2003-08-04 6:00 ` Bart Schaefer
2003-09-07 17:57 ` Wayne Davison
2003-09-07 21:24 ` DervishD
2003-09-08 3:27 ` Dan Nelson
2003-09-08 9:45 ` DervishD
2003-09-08 15:57 ` Dan Nelson
2003-09-08 22:01 ` DervishD
2003-09-08 9:47 ` Phil Pennock
2003-09-08 10:59 ` DervishD
2003-09-08 17:55 ` Wayne Davison
2003-09-08 22:48 ` Phil Pennock
2003-09-10 20:00 ` Wayne Davison
2003-09-10 19:57 ` Wayne Davison
2003-09-11 6:50 ` Oliver Kiddle
2003-08-04 2:57 ` Dan Nelson
2003-08-04 10:45 ` Nikolai Weibull
2003-08-04 9:15 ` Zefram
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030803223949.GA18476@binome.blorf.net \
--to=wayned@users.sourceforge.net \
--cc=lone-star@home.se \
--cc=zsh-users@sunsite.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).