[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mercurial
Subject:    Re: [PATCH] show choices when ambiguous command is specified
From:       Thomas Arendsen Hein <thomas () intevation ! de>
Date:       2006-02-28 4:45:48
Message-ID: 20060228044548.GA5140 () intevation ! de
[Download RAW message or body]

* TK Soh <teekaysoh@yahoo.com> [20060228 02:21]:
> --- Thomas Arendsen Hein <thomas@intevation.de> wrote:
> > * Benoit Boissinot <bboissin@gmail.com> [20060227 06:00]:
> > > On 2/27/06, TK Soh <teekaysoh@yahoo.com> wrote:
> > > > --- Thomas Arendsen Hein <thomas@intevation.de> wrote:
> > > > > Can you make a second patch applying on top of this one to ignore
> > > > > debug commands and sort the output alphabetically?
> > > >
> > > > I will work on the sorting. But ambiguity applies to the debug commands too, so I feel it
> > > > might be confusing if no command list shows up when user type in 'hg debug'. No?
> > > >
> > > maybe only list the debug commands if it begins with 'debug'
> > 
> > The bash completion hides all debug commands, unless all matching
> > commands start with 'debug', i.e. without any extension loaded,
> > "hg d" won't show you debug commands, but should execute diff (this
> > currently doesn't work!) and "hg de" will tell you debug commands.
> > If you define a new command in an extension which starts with "de",
> > too, then you need to type more to see debug commands.
> 
> I am a little confused here. What kind of error message should be printed if 'hg de' has been
> entered, assuming 'hg d' will only match 'hg diff'?

In case of "hg de" all _matching_commands_ start with 'debug', so
print the debug commands.

Thomas

-- 
Email: thomas@intevation.de
http://intevation.de/~thomas/
_______________________________________________
Mercurial mailing list
Mercurial@selenic.com
http://selenic.com/mailman/listinfo/mercurial
[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic