karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré ...@nanthrax.net>
Subject Re: Tab Completion Trunk
Date Sun, 29 Sep 2013 06:23:25 GMT
I'm -1 for [3] as the most insteresting on the root level: it's where 
you have all commands in the completer, which is what we should avoid 
for subshell. By the way, feature:list doesn't switch automatically to 
the feature subshell (you can use feature:list on the root level, or any 
other levels, or go explicitely to the feature subshell).

I will add the:


- if subshell.completion.only=false, the completer will complete to all 
subshells, commands, aliases (on any level)
- if subshell.completion.only=true, the completer will complete to all 
subshells and aliases depending of the level


On 09/27/2013 09:42 PM, Achim Nierbeck wrote:
> +1 for giving the user an easy way of en/dis-abling of such a feature.
> Second I'd prefer variant 2 with a slight varian, or better a
> [3] - I prefer to use subshell with completion on subshell, but when I'm on
> the "root"-Shell I
> do have global completion, and a feature:list doesn't switch automatically
> to the feature sub-shell
> regards, Achim
> 2013/9/27 nseb <seb_nicouleau@hotmail.com>
>> +1
>> An option will give the user the choice.
>> In fact, it all depends on what phase we are in, using the shell is not
>> necessarily the same.
>> It is also necessary that this option can be enabled / disabled from the
>> shell.
>> --
>> View this message in context:
>> http://karaf.922171.n3.nabble.com/Tab-Completion-Trunk-tp4029755p4029768.html
>> Sent from the Karaf - Dev mailing list archive at Nabble.com.

Jean-Baptiste Onofré
Talend - http://www.talend.com

View raw message