Tag: Branch: Tree: 12324856c6

master

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '12324856c6'

${ noResults }

Commit Graph

10 Commits (12324856c6645c2e71c4dfcf5ef12313c989b387)

Author	SHA1	Message	Date
Bob Bonifield	f082d7a245	Making auto-correction off by default ... - Allows for the user to turn on auto-correction using the $ENABLE_CORRECTION variable - Adds aliases regardless of variable assignment to aid users that use setopt to turn correction back on in their zshrc	12 years ago
Morgan Larosa	682961e930	Add a configuration option to disable autocorrect	14 years ago
Andrew Ash	4e0b5be145	Fix spurious correction with sudo vim ... user@host:~ $ sudo vim /etc/rc.conf zsh: correct 'vim' to '.vim' [nyae]? http://www.zsh.org/mla/users/2012/msg00028.html	14 years ago
Daniel Hahler	70e51186ec	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.	14 years ago
James Rowe	6efc79c74e	Don't correct hpodder commands.	16 years ago
James Rowe	6774490a46	Don't auto-correct ebuild commands. ... It breaks "ebuild <foo> manifest", as there are Manifest files in the directory.	16 years ago
Robby Russell	98d56a3097	Adding a nocorrect for the heroku command as it was getting triggered by heroku logs.	17 years ago
To1ne	e429ff9e2b	no correction on gist	17 years ago
To1ne	dfb3fb5a0a	No correction on mkdir + removed duplicate nocorrect mv	17 years ago
James Cox	f363c025da	put everything in lib	17 years ago
James Cox	1b784bbf4d	make correction work; this is a nicer way of handling typos in commands	17 years ago