Permalink
Browse files

Only `setopt correct`, not "correct_all".

Using the correct_all option is too distracting, and needs a lot of
`nocorrect` aliases to work around this.

Using only "correct" to correct the command itself is more friendly.
  • Loading branch information...
1 parent c133f41 commit 70e51186ec3f67b1126339c7570bd9f6549f0408 @blueyed blueyed committed Dec 16, 2011
Showing with 2 additions and 10 deletions.
  1. +2 −10 lib/correction.zsh
View
12 lib/correction.zsh
@@ -1,10 +1,2 @@
-setopt correct_all
-
-alias man='nocorrect man'
-alias mv='nocorrect mv'
-alias mysql='nocorrect mysql'
-alias mkdir='nocorrect mkdir'
-alias gist='nocorrect gist'
-alias heroku='nocorrect heroku'
-alias ebuild='nocorrect ebuild'
-alias hpodder='nocorrect hpodder'
+# correct commands, but not any arguments (correct_all would do that)
+setopt correct

0 comments on commit 70e5118

Please sign in to comment.