Zsh Mailing List Archive
Messages sorted by:
Re: help with understanding diffs in startup files
- X-seq: zsh-users 1189
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-users@xxxxxxxxxxxxxxx
- Subject: Re: help with understanding diffs in startup files
- Date: Mon, 8 Dec 1997 08:14:06 -0800
- In-reply-to: <199712081042.FAA01749@xxxxxxxxxxxxxxx>
- In-reply-to: <199712081115.LAA29680@xxxxxxxxxxxxxxxx>
- In-reply-to: <199712081124.GAA02299@xxxxxxxxxxxxxxx>
- In-reply-to: <199712081211.MAA31918@xxxxxxxxxxxxxxxx>
- References: <199712081042.FAA01749@xxxxxxxxxxxxxxx> <199712081115.LAA29680@xxxxxxxxxxxxxxxx> <199712081124.GAA02299@xxxxxxxxxxxxxxx> <199712081211.MAA31918@xxxxxxxxxxxxxxxx>
On Dec 8, 5:42am, Timothy J Luoma wrote:
} Subject: help with understanding diffs in startup files
} Well, there's this Linux account I have where there is some system file
} which is setting up some variables after my .zshenv. Really annoying. Sun
} and NeXT have never had this problem.
On Dec 8, 11:15am, Andrew Main wrote:
} It is a particular problem with Slackware.
On Dec 8, 6:24am, Timothy J Luoma wrote:
} This is Redhat I think
The contributed binary RPM for zsh-3.0.5 installs system-wide init files in
the directory /etc/zsh/:
I haven't looked to see what's in each of them, because I build zsh myself,
so I didn't install the binary RPM.
On Dec 8, 12:11pm, Andrew Main wrote:
} Subject: Re: help with understanding diffs in startup files
} Timothy J Luoma wrote:
} >I've always just used one init file. Perhaps this would be a good time to
} >learn what should go in what file.
} Actually, the division isn't that simple. .zshenv should set up your
} normal shell environment, including many options, most functions and
} most variables. .zshrc should set up your interactive shell environment,
} including many options, all bindkeys and compctls, aliases, and functions
} and variables that are only used interactively (such as compctl functions
} and $HISTCHARS). .zprofile (or .zlogin if you prefer) should contain
} commands to run when you log in, and should not affect the environment
} at all.
I agree with everything but the last clause. There's no reason to say
that .zprofile or .zlogin should not affect the environment; they should
contain commands, possibly including environment settings, that need to
happen at least once when you log in, but that then remain constant.
For example, my .zlogin does a number of tests of what host type I'm on,
what software is installed at what versions and where, and so on, and
manipulates the environment accordingly. But that doesn't need to happen
every time I start any interactive shell -- unless of course a misguided
/etc/zshrc steps on my changes every time.
Bart Schaefer Brass Lantern Enterprises
Messages sorted by: