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

Re: [Fwd: bash completion for subversion]

From: Martin Blais <martin.blais_at_gmail.com>
Date: 2004-11-09 04:49:54 CET

some notes below.

On Mon, 08 Nov 2004 22:44:43 +0000, Julian Foad
<julianfoad@btopenworld.com> wrote:
> Brian W. Fitzpatrick wrote:
> > Philip,
> >
> > I've just tested this out, and it works as expected. What do you
> > think? Do you want to replace your script with this or just have it
> > live side-by-side? Let me know what you think and I'll commit it.
> This runs "svn" (or "svnadmin") every time you ask for a completion, which is slow.

IMO not a problem for completion, completion can be "slow"--if the
definition of slow is the few microseconds it takes for svn to display
the help.

> This doesn't remove unambiguous abbreviations such as "up" from its list of
> candidates, despite the comment that says it does. Thus if you ask for
> completion of "up", it offers "up" and "update" whereas the more useful thing
> is to just complete it as "update".

indeed, you could add a cmd to filter out short abbrevs or something.
just an idea.

> This script starts with "#!/bin/sh" but (a) it is Bash-specific, and (b)
> there's no point in being able to run it as a program, it has to be sourced
> in-line by the instance of Bash that wants the completion. So that line should
> be removed.

sure, feel free to do so, it's all yours now.

> It would be nice if you could attach this with MIME type text/plain rather than
> application/octet-stream.

sorry i can't, i use gmail now, i have no option to do that...

> We would probably want to remove the CVS/RCS keyword lines if we store this in
> the Subversion repository.



To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Nov 9 06:16:35 2004

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.