1
0
mirror of git://git.code.sf.net/p/zsh/code synced 2024-11-19 13:33:52 +01:00
zsh/StartupFiles/zshenv

32 lines
1.5 KiB
Plaintext
Raw Normal View History

1999-04-15 20:05:38 +02:00
#
# Generic .zshenv file for zsh
1999-04-15 20:05:38 +02:00
#
# .zshenv is sourced on ALL invocations of the shell, unless the -f option is
# set. It should NOT normally contain commands to set the command search path,
# or other common environment variables unless you really know what you're
# doing. E.g. running "PATH=/custom/path gdb program" sources this file (when
# gdb runs the program via $SHELL), so you want to be sure not to override a
# custom environment in such cases. Note also that .zshenv should not contain
# commands that produce output or assume the shell is attached to a tty.
1999-04-15 20:05:38 +02:00
#
# THIS FILE IS NOT INTENDED TO BE USED AS /etc/zshenv, NOR WITHOUT EDITING
return 0 # Remove this line after editing this file as appropriate
# This kludge can be used to override some installations that put aliases for
# rm, mv, etc. into the system profiles. Just be sure to put "unalias alias"
# in your own rc file(s) if you use this.
alias alias=:
1999-04-15 20:05:38 +02:00
# Some people insist on setting their PATH here to affect things like ssh.
# Those that do should probably use $SHLVL to ensure that this only happens
# the first time the shell is started (to avoid overriding a customized
# environment). Also, the various profile/rc/login files all get sourced
# *after* this file, so they will override this value. One solution is to
# put your path-setting code into a file named .zpath, and source it from
# both here (if we're not a login shell) and from the .zprofile file (which
# is only sourced if we are a login shell).
if [[ $SHLVL == 1 && ! -o LOGIN ]]; then
source ~/.zpath
fi