Re: ~/.zshenv or ~/.zprofile

[Phil Pennock <phil.pennock@xxxxxxxxxxx>]

On 2003-09-08 at 10:55 -0700, Wayne Davison wrote:
> Another solution for that is to use ~/.ssh/environment (as long as the
> "PermitUserEnvironment yes" option is set in the sshd_config file).  It
> also has the benefit of working regardless of what login shell you might
> have on a particular machine.

Heh -- on various Solaris boxes here, my .zshenv (or system zshenv)
builds $PATH at run-time, by setting $path to uniqueness and adding
various globs using zsh glob modifiers.

typeset -aU path
typeset -x PATH
path=(
	/foo
	/opt/special-priority/bin
	/bar
	/usr/*/bin(/)
	/opt/*/bin(/)
     )

I could mess around with cronjobs to keep that more up-to-date.  I could
do so and create a file in bourne-compatible syntax, sourced from
/etc/profile.  I could do many things.

I keep things simple and set $path in zshenv -- it's understandable and
doesn't lead to other people having to wade through docs which I've
written or reverse-engineer stuff themselves.

If set in /etc/zshenv then this stuff can contain some highly
system-dependent locations.

zsh rocks.
-- 
2001: Blogging invented. Promises to change the way people bore strangers with
banal anecdotes about their pets. <http://www.thelemon.net/issues/timeline.php>