[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [PATCH] bash_completion: improvement, fixes and tests [was: Re: subversion and programmable completion]

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2003-07-26 04:37:02 CEST

Jack Repenning <jrepenning@collab.net> writes:

> At 2:55 AM +0100 7/26/03, Philip Martin wrote:
>>My argument is that "svn --help " breaks further completion so I don't
>>want to completion to suggest it. The "--help" option is not special
>>here, all options break completion if they occur first, so "svn -v "
>>breaks further completion even though "svn -v st" is a valid command.
> Once you get to the --stuff, your completion is broken anyway, isn't
> it? But there are potentially completable things out there. Unless
> you wanted to universally encourage the neologism
> svn commit filename --flag

I'm not sure I understand what you mean, options can go in any order
after the sub-command. Completion for

   svn commit -
   svn commit SomeFile -
   svn commit -m foo SomeFile AnotherFile -

all suggest a bunch of commit options.

Do you mean that completion for --username does file completion? Yes,
it could do something more sophisticated than file completion (suggest
$USER perhaps), but that doesn't appear to me to be a reason for the
--help option to be suggested as a completion for "svn". What do we
gain by encouraging "svn --help" over "svn help"?

Philip Martin
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jul 26 04:37:52 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.