Skip to content

Only `setopt correct`, not "correct_all". #749

Merged
merged 1 commit into from Mar 27, 2013
@blueyed
blueyed commented Dec 16, 2011

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.

@blueyed blueyed 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.
70e5118
@cicloid
cicloid commented Dec 30, 2011

:+1:

I have noticed this also.

@tubbo
tubbo commented Jan 9, 2012

+1

@pigmonkey

+2

@Soares
Soares commented Jan 24, 2012

+1, I always override this myself.

@akamch
akamch commented Feb 9, 2012

:+1:
~ » sudo aptitude
zsh: correct 'aptitude' to '.aptitude' [nyae]? :punch:

@rwz
rwz commented Mar 8, 2012

:+1:

$ git checkout -b pp/new_feature
zsh: correct 'pp/new_feature' to 'app/new_feature' [nyae]? n
$ heroku logs -t
zsh: correct 'logs' to 'log' [nyae]? n
@haihappen

Yeah, please accept this pull request!

@zhuangya

please accept

really troubles me..

$ rake deploy 
zsh: correct 'deploy' to '_deploy' [nyae]? 

@neoascetic

+1 on this
(moved to antigen and my own repo)

@F30
F30 commented Oct 14, 2012

Yet another +1

@shenrui01

Yet another +1

@jmatth
jmatth commented Nov 21, 2012

+1. Overriding in my own fork now.

@plalloni

+1

@robbyrussell robbyrussell merged commit b8b241f into robbyrussell:master Mar 27, 2013
@robbyrussell
Owner

Giving in... it's annoyed me enough times too. :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.