[Gnu-arch-users] Re: tla-bash-complete usability

[Jonas Diemer]

>  but revision completion is also the most ressource
> > intense task: The script would have to recursively get all existing
> > versions, then get all revision for each version and finally
> > concenate them together.
> 
> I don't understand why.  It should interactively complete each piece
> of the version, so that when it comes time to list revisions, you only
> have the revisions associated with that version.  Ex:
> 
> tla replay --exact cat[TAB]
> cat--branch1
> cat--branch2
> tla replay --exact cat--branch1[TAB]
> cat--branch1--1.0
> cat--branch1--2.0
> tla replay --exact cat--branch1--2.0[TAB]
> cat--branch1--2.0--patch-3
> ...
> cat--branch1--2.0--patch-9
> 

Yeah, that's right. But this will, however, bess up this completion:

tla get [tab]
<avaliable options>
cat--branch1--2.0--patch-3
..
cat--branch1--2.0--patch-9
<all other revisions of other cats>

And still, the tla-bash-complete script needs to return all possible
revisions. Just returning all categories first (and later complete
branch etc. based on $cur) will result in this behaviour:

tla get ca[tab]
tla get cat [tab]

As you see, bash will complete cat but then add a space...

There's probably a way around this, but I don't think its necessary
(maybe later if -A is taken into respect and we try and complete for a
remote archive).

I have done full revision completion now (currently only for
revisions|tag|cachedrevs|log-ls), you might wanna check that out.


Jonas

PS: CC me in your replies for now, until I receive mail from the list
again.