Browse files

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
  • Loading branch information...
1 parent 00a190b commit eddab5034cb19caa99a1a0e381de4dcf63ef0fe0 @evansj evansj committed Oct 1, 2009
Showing with 8 additions and 8 deletions.
  1. +0 −8 lib/misc.zsh
  2. +8 −0 oh-my-zsh.sh
View
8 lib/misc.zsh
@@ -7,11 +7,3 @@ bindkey "^[m" copy-prev-shell-word
## jobs
setopt long_list_jobs
-
-# Check for updates on initial load...
-if [ "$DISABLE_AUTO_UPDATE" = "true" ]
-then
- return
-else
- /bin/sh $ZSH/tools/check_for_upgrade.sh
-fi
View
8 oh-my-zsh.sh
@@ -6,3 +6,11 @@ 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
+ /bin/sh $ZSH/tools/check_for_upgrade.sh
+fi

1 comment on commit eddab50

@robbyrussell

FYI, this didn't seem to fix it for someone else. Looks like we need to set the PATH before we load up zsh stuff or find another way to load the PATH during the upgrade process

Please sign in to comment.