ohmyzsh/oh-my-zsh.sh

# Initializes Oh My Zsh

# add a function path
fpath=($ZSH/functions $fpath)

# Load all of the config files in ~/oh-my-zsh that end in .zsh
# TIP: Add files you don't want in git to .gitignore
for config_file ($ZSH/lib/*.zsh) source $config_file

# Load all of your custom configurations from custom/
for config_file ($ZSH/custom/*.zsh) source $config_file

# Check for updates on initial load...
if [ "$DISABLE_AUTO_UPDATE" = "true" ]
then
  return
else
  /usr/bin/env zsh $ZSH/tools/check_for_upgrade.sh
fi

unset config_file
Moving the loading of all .zsh files into a different file so that we can remove zshrc from the repository 2009-09-01 22:41:18 +08:00			`# Initializes Oh My Zsh`

adding homebrew completions - and a function dir 2009-10-26 12:47:23 +08:00			`# add a function path`
			`fpath=($ZSH/functions $fpath)`

Moving the loading of all .zsh files into a different file so that we can remove zshrc from the repository 2009-09-01 22:41:18 +08:00			`# Load all of the config files in ~/oh-my-zsh that end in .zsh`
			`# TIP: Add files you don't want in git to .gitignore`
Moving all zsh config options into a lib/ subdirectory to make way for some upcoming changes to directory structure and configuration options 2009-09-23 22:43:36 +08:00			`for config_file ($ZSH/lib/*.zsh) source $config_file`
Moving some example files into custom/ 2009-09-23 23:02:58 +08:00
			`# Load all of your custom configurations from custom/`
			`for config_file ($ZSH/custom/*.zsh) source $config_file`
run update check after running custom configuration scripts. This means we are running it after $PATH has potentially been set up, which means it's more likely that commands like "git" will be found 2009-10-01 15:55:07 +08:00
			`# Check for updates on initial load...`
			`if [ "$DISABLE_AUTO_UPDATE" = "true" ]`
			`then`
			`return`
			`else`
Based on a suggestion from robbyrussel, using env for greater compatibility. 2009-12-14 03:38:37 +08:00			`/usr/bin/env zsh $ZSH/tools/check_for_upgrade.sh`
run update check after running custom configuration scripts. This means we are running it after $PATH has potentially been set up, which means it's more likely that commands like "git" will be found 2009-10-01 15:55:07 +08:00			`fi`
Unsetting config_file after loading config 2010-05-07 12:13:59 +08:00
			`unset config_file`