configs/scatterd-dotfiles
1
0
Fork 0
Code Issues 2 Pull requests 1 Projects Releases Packages Wiki Activity Actions
scatterd-dotfiles/zshenv

30 lines
701 B
Text
Raw Normal View History

Detect if `~/.zshenv.local` changes PATH and suggest `.zshrc` instead Warn people who might have PATH and similar configuration in their `~/.zshenv.local` that they should upgrade to `~/.zshrc.local` since that's a much better phase for such configuration. This is for backwards compatibility with people's personal configurations from pre-El Capitan days. The generic `.zshenv` file from zsh distribution[1] advises: > .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. [1]: http://sourceforge.net/p/zsh/code/ci/master/tree/StartupFiles/zshenv
2015-10-05 01:43:32 +02:00
local _old_path="$PATH"
Add zshenv file From the [Zsh manual](http://zsh.sourceforge.net/Intro/intro_3.html): > '.zshenv' is sourced on all invocations of the shell, unless the -f option is > set. It should contain commands to set the command search path, plus other > important environment variables. `.zshenv' should not contain commands that > produce output or assume the shell is attached to a tty. Why is this important? [Alfred](http://www.alfredapp.com/) workflows run in non-interactive shells. When the `$PATH` is set, or `rbenv` is initialized, in `zshrc` instead of `zshenv`, those workflows will not use the correct Ruby version and might not have access to certain bin files, such as those from `$HOME/.bin/` or Homebrew.
2014-07-27 22:54:36 -04:00
# Local config
[[ -f ~/.zshenv.local ]] && source ~/.zshenv.local
Detect if `~/.zshenv.local` changes PATH and suggest `.zshrc` instead Warn people who might have PATH and similar configuration in their `~/.zshenv.local` that they should upgrade to `~/.zshrc.local` since that's a much better phase for such configuration. This is for backwards compatibility with people's personal configurations from pre-El Capitan days. The generic `.zshenv` file from zsh distribution[1] advises: > .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. [1]: http://sourceforge.net/p/zsh/code/ci/master/tree/StartupFiles/zshenv
2015-10-05 01:43:32 +02:00
if [[ $PATH != $_old_path ]]; then
# `colors` isn't initialized yet, so define a few manually
typeset -AHg fg fg_bold
Only colorize warning messages if stderr is a tty This is to avoid outputting ANSI escape codes to scripts and log files.
2015-10-16 18:22:46 +02:00
if [ -t 2 ]; then
fg[red]=$'\e[31m'
fg_bold[white]=$'\e[1;37m'
reset_color=$'\e[m'
else
fg[red]=""
fg_bold[white]=""
reset_color=""
fi
Detect if `~/.zshenv.local` changes PATH and suggest `.zshrc` instead Warn people who might have PATH and similar configuration in their `~/.zshenv.local` that they should upgrade to `~/.zshrc.local` since that's a much better phase for such configuration. This is for backwards compatibility with people's personal configurations from pre-El Capitan days. The generic `.zshenv` file from zsh distribution[1] advises: > .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. [1]: http://sourceforge.net/p/zsh/code/ci/master/tree/StartupFiles/zshenv
2015-10-05 01:43:32 +02:00
cat <<MSG >&2
${fg[red]}Warning:${reset_color} your \`~/.zshenv.local' configuration seems to edit PATH entries.
Please move that configuration to \`.zshrc.local' like so:
${fg_bold[white]}cat ~/.zshenv.local >> ~/.zshrc.local && rm ~/.zshenv.local${reset_color}
(called from ${(%):-%N:%i})
MSG
fi
unset _old_path
Reference in a new issue Copy permalink