All of lore.kernel.org
 help / color / mirror / Atom feed
* More use of levenshtein?
@ 2012-06-01 19:04 Junio C Hamano
  2012-06-02 10:26 ` Nguyen Thai Ngoc Duy
  0 siblings, 1 reply; 4+ messages in thread
From: Junio C Hamano @ 2012-06-01 19:04 UTC (permalink / raw)
  To: git

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, I do have maint-1.7.8 branch in my private repository.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: More use of levenshtein?
  2012-06-01 19:04 More use of levenshtein? Junio C Hamano
@ 2012-06-02 10:26 ` Nguyen Thai Ngoc Duy
  2012-06-02 11:37   ` David Michael Barr
  2012-06-02 22:55   ` Junio C Hamano
  0 siblings, 2 replies; 4+ messages in thread
From: Nguyen Thai Ngoc Duy @ 2012-06-02 10:26 UTC (permalink / raw)
  To: Junio C Hamano; +Cc: git

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: More use of levenshtein?
  2012-06-02 10:26 ` Nguyen Thai Ngoc Duy
@ 2012-06-02 11:37   ` David Michael Barr
  2012-06-02 22:55   ` Junio C Hamano
  1 sibling, 0 replies; 4+ messages in thread
From: David Michael Barr @ 2012-06-02 11:37 UTC (permalink / raw)
  To: Nguyen Thai Ngoc Duy; +Cc: Junio C Hamano, git

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: More use of levenshtein?
  2012-06-02 10:26 ` Nguyen Thai Ngoc Duy
  2012-06-02 11:37   ` David Michael Barr
@ 2012-06-02 22:55   ` Junio C Hamano
  1 sibling, 0 replies; 4+ messages in thread
From: Junio C Hamano @ 2012-06-02 22:55 UTC (permalink / raw)
  To: Nguyen Thai Ngoc Duy; +Cc: git

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.

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2012-06-02 22:56 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-06-01 19:04 More use of levenshtein? Junio C Hamano
2012-06-02 10:26 ` Nguyen Thai Ngoc Duy
2012-06-02 11:37   ` David Michael Barr
2012-06-02 22:55   ` Junio C Hamano

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.