Junio C HamanoPerhaps we could go one step further when we issue this error message?
$ git checkout -b jc/ls-files-i-dir maitn-1.7.8 fatal: git checkout: updating paths is incompatible with switching branches. Did you intend to checkout 'maitn-1.7.8' which can not be resolved as commit?
Yes, I do have maint-1.7.8 branch in my private repository.
Nguyen Thai Ngoc DuyRe: More use of levenshtein?
On Sat, Jun 2, 2012 at 2:04 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Perhaps we could go one step further when we issue this error message? > > $ git checkout -b jc/ls-files-i-dir maitn-1.7.8 > fatal: git checkout: updating paths is incompatible with switching branches. > Did you intend to checkout 'maitn-1.7.8' which can not be resolved as commit?
Yes, please. Also to correct misspelled option names.
In case there are more than one candidate, we should print extra info (for commands or options, it's one line description; for refs, probably commit subject line)
-- Duy
David Michael BarrRe: More use of levenshtein?
On Sat, Jun 2, 2012 at 8:26 PM, Nguyen Thai Ngoc Duy <pclouds@gmail.com> wrote:
> On Sat, Jun 2, 2012 at 2:04 AM, Junio C Hamano <gitster@pobox.com> wrote: >> Perhaps we could go one step further when we issue this error message? >> >> $ git checkout -b jc/ls-files-i-dir maitn-1.7.8 >> fatal: git checkout: updating paths is incompatible with switching branches. >> Did you intend to checkout 'maitn-1.7.8' which can not be resolved as commit? > > Yes, please. Also to correct misspelled option names. > > In case there are more than one candidate, we should print extra info > (for commands or options, it's one line description; for refs, > probably commit subject line)
This and a functional implementation of "help.autocorrect = prompt." I think we now have the bits and pieces to do it right.
-- David Barr
Junio C HamanoRe: More use of levenshtein?
Nguyen Thai Ngoc Duy <pclouds@gmail.com> writes:
> Yes, please. Also to correct misspelled option names. > > In case there are more than one candidate, we should print extra info > (for commands or options, it's one line description; for refs, > probably commit subject line)
I do not think either is a good idea. We are talking about "typo", the user knew what he wanted, just didn't spell it correctly.