zsh-users
 help / color / mirror / code / Atom feed
From: Russell Hoover <rj@panix.com>
To: zsh-users@sunsite.dk
Subject: Do I really need a .zshenv?
Date: Mon, 27 Aug 2001 15:38:04 -0400	[thread overview]
Message-ID: <20010827153804.A16051@panix.com> (raw)

I have a ~/.zshenv in which I've set 25 to 30 environment variables.
My ISP's /etc/zprofile sets about six env vars which I've re-set
in my ~/.zshrc.

( The order of zsh startup files on my system is:

(1)  ~/.zshenv
(2)  /etc/zprofile
(3)  ~/.zprofile
(4)  ~/.zshrc )

I'd like to avoid, if possible, having *two* separate startup files,
both of which contain env vars.

I'd like to move everything that's in my ~/.zshenv over into my ~/.zshrc.

That way, as I see it, I won't have to worry about /etc/zprofile ever
changing, or having more variables added, and then me having to re-set
anything.  It's basically just an annoyance that /etc/zprofile overwrites
~/.zshenv.

(And since my ~/.zshrc has a fairly long list of aliases, I can move all
them into their own file and source that file from within ~/.zshrc.)

(I also have a small ~/.zprofile.)

My question: is there any reason for me to keep a .zshenv, instead of
taking all the settings that are in it, and putting them in ~/.zshrc,
and just getting rid of ~/.zshenv altogether?

Is ~/.zshrc sourced *only* in interactive shells and not on *all*
invocations of the shell (as ~/.zshenv is)?  If so, how much (why) would
that matter to me?  (scripts, etc?)    Thanks for any suggestions.

-- 
                                 // rj@panix.com //


             reply	other threads:[~2001-08-27 19:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-27 19:38 Russell Hoover [this message]
2001-08-27 20:41 ` Bart Schaefer

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=20010827153804.A16051@panix.com \
    --to=rj@panix.com \
    --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).