Browse code

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

Jon Evans authored on 01/10/2009 at 07:55:07
Showing 2 changed files
... ...
@@ -7,11 +7,3 @@ bindkey "^[m" copy-prev-shell-word
7 7
 
8 8
 ## jobs
9 9
 setopt long_list_jobs
10
-
11
-# Check for updates on initial load...
12
-if [ "$DISABLE_AUTO_UPDATE" = "true" ]
13
-then
14
-  return
15
-else
16
-  /bin/sh $ZSH/tools/check_for_upgrade.sh
17
-fi
... ...
@@ -6,3 +6,11 @@ for config_file ($ZSH/lib/*.zsh) source $config_file
6 6
 
7 7
 # Load all of your custom configurations from custom/
8 8
 for config_file ($ZSH/custom/*.zsh) source $config_file
9
+
10
+# Check for updates on initial load...
11
+if [ "$DISABLE_AUTO_UPDATE" = "true" ]
12
+then
13
+  return
14
+else
15
+  /bin/sh $ZSH/tools/check_for_upgrade.sh
16
+fi