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