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

Re: [PATCH] improved bash completion v2

From: Fabien COELHO <fabien_at_coelho.net>
Date: 2005-11-17 17:46:46 CET

> OK. (For "pset" and "pedit", then, it shouldn't suggest "--revision" when
> the property name is not a revprop, but I don't think that's very important.)

Indeed. Easy to fix.

>>>> + COMPREPLY=( '' )
>>
>> I do want to stop the file completion, because this case is triggered when
>> no more arguments are expected (e.g. you're doing a cp and you already gave
>> 2 arguments, whatever you're adding is garbage and should trigger an error
>> of the completion, but not a standard file completion).
>
> That's fine if you can find a way to stop the completion, but what you're
> doing doesn't stop it. It stops _file name_ completion, but it doesn't stop
> _completion_. It just makes Bash think the word you have started is OK, and
> considers it complete:

Ok,

I really want a beep, but compgen does not seem to provide a way to
'really no choice'. Giving no choices is interpreted as 'try next completion'.

> Here's a kind-of-ugly idea that has the sort of effect you want:
>> COMPREPLY=( 'bash_completion:' 'only two arguments wanted' )

Ugly but funny. I'll try a simpler: echo -e "\nsome message\a" >&2
but it does not solve the inserted space.

-- 
Fabien.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Nov 17 17:47:53 2005

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