From: Zefram <zefram@fysh.org>
To: Nikolai Weibull <lone-star@home.se>
Cc: zsh-users@sunsite.dk
Subject: Re: ~/.zshenv or ~/.zprofile
Date: Mon, 4 Aug 2003 10:15:57 +0100 [thread overview]
Message-ID: <20030804091557.GA22717@fysh.org> (raw)
In-Reply-To: <20030803221858.GA2720@puritan.pcp.ath.cx>
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.
When I run an interactive zsh, I want my customised environment
from ~/.zshenv regardless of what the parent process was doing.
$SHELL shouldn't be being used for any other purpose; a program that
wants a shell to interpret a command it's just generated should be using
/bin/sh directly, or, if it wants zsh, should be using /usr/bin/zsh -f.
Unfortunately there are many programs that are not well-behaved, and
use $SHELL as a non-interactive command interpreter, expecting it to
interpret some particular shell command language. With make and procmail
(both of which are badly-behaved in this manner), it is wise to always
explicitly set SHELL=/bin/sh in the configuration file.
-zefram
prev parent reply other threads:[~2003-08-04 9:16 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
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 [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030804091557.GA22717@fysh.org \
--to=zefram@fysh.org \
--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).