Re: Tab Completion Trunk

2013-09-27 Thread nseb
Ok , but we also lost another feature, if I type feature:install j and tab,
it offers me the list of features installed beginning by the letter j (in my
case )

All these behaviors are very recent, I'd say two months on the version of
the trunk.



--
View this message in context: 
http://karaf.922171.n3.nabble.com/Tab-Completion-Trunk-tp4029755p4029759.html
Sent from the Karaf - Dev mailing list archive at Nabble.com.


Re: Tab Completion Trunk

2013-09-27 Thread Jean-Baptiste Onofré
Only installed, or also uninstalled (it shound be only the uninstalled 
features) ?


Regards
JB

On 09/27/2013 10:59 AM, nseb wrote:

Ok , but we also lost another feature, if I type feature:install j and tab,
it offers me the list of features installed beginning by the letter j (in my
case )

All these behaviors are very recent, I'd say two months on the version of
the trunk.



--
View this message in context: 
http://karaf.922171.n3.nabble.com/Tab-Completion-Trunk-tp4029755p4029759.html
Sent from the Karaf - Dev mailing list archive at Nabble.com.



--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com


Re: Tab Completion Trunk

2013-09-27 Thread Jean-Baptiste Onofré

By the way, if you do:

karaf@root feature
karaf@root:feature install jTAB

is it OK there ?

Regards
JB

On 09/27/2013 10:59 AM, nseb wrote:

Ok , but we also lost another feature, if I type feature:install j and tab,
it offers me the list of features installed beginning by the letter j (in my
case )

All these behaviors are very recent, I'd say two months on the version of
the trunk.



--
View this message in context: 
http://karaf.922171.n3.nabble.com/Tab-Completion-Trunk-tp4029755p4029759.html
Sent from the Karaf - Dev mailing list archive at Nabble.com.



--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com


Re: Tab Completion Trunk

2013-09-27 Thread nseb
Yes, only if we are in subshell.

I still maintain that the system was better before because bcp more
interactive and what we call a shell.
Currently, we are developing bundles, I go through the installation of
feature, I have to check my bundle is properly activated, potentially make a
update or refresh a bundle, a bundle of test command, see the logs.
With the new method is tedious, before that I was faster because I
autocomplete from any location.

the shell mode loses much of its interest.



--
View this message in context: 
http://karaf.922171.n3.nabble.com/Tab-Completion-Trunk-tp4029755p4029763.html
Sent from the Karaf - Dev mailing list archive at Nabble.com.


Re: Tab Completion Trunk

2013-09-27 Thread Jean-Baptiste Onofré

I get your point.

The purpose of subshell is to avoid a huge number of commands, 
especially when you type TAB.


Imagine when you add Camel, CXF, and other projects in Karaf: it's not 
easy with the bunch of commands displayed.


In any case, if you know the commands, you can still use actual command 
(like bundle:start, bundle:stop), no need to go into the subshell.


However, it's fair enough to start a discussion:

[1] I prefer to use subshell with completion on subshell
[2] I prefer to use subshell with global complete for all commands

Let see what the other users prefer.

Regards
JB

On 09/27/2013 02:39 PM, nseb wrote:

Yes, only if we are in subshell.

I still maintain that the system was better before because bcp more
interactive and what we call a shell.
Currently, we are developing bundles, I go through the installation of
feature, I have to check my bundle is properly activated, potentially make a
update or refresh a bundle, a bundle of test command, see the logs.
With the new method is tedious, before that I was faster because I
autocomplete from any location.

the shell mode loses much of its interest.



--
View this message in context: 
http://karaf.922171.n3.nabble.com/Tab-Completion-Trunk-tp4029755p4029763.html
Sent from the Karaf - Dev mailing list archive at Nabble.com.



--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com


Re: Tab Completion Trunk

2013-09-27 Thread Christian Schneider

+1

An option will give the user the choice. I would set the option to 
global completion by default though so people

have their old behaviour.

I personally am ok with the number of possible completions global 
completion produces. By typing the start of the command you can narrow 
down the list easily.


Christian


On 27.09.2013 14:46, Jean-Baptiste Onofré wrote:
Another thing that I can do is to define a property in 
etc/org.apache.karaf.shell.cfg to let the user decide: global 
completion or subshell completion.


Like this, each user can use what he prefers.

Regards
JB

On 09/27/2013 02:39 PM, nseb wrote:

Yes, only if we are in subshell.

I still maintain that the system was better before because bcp more
interactive and what we call a shell.
Currently, we are developing bundles, I go through the installation of
feature, I have to check my bundle is properly activated, potentially 
make a

update or refresh a bundle, a bundle of test command, see the logs.
With the new method is tedious, before that I was faster because I
autocomplete from any location.

the shell mode loses much of its interest.



--
View this message in context: 
http://karaf.922171.n3.nabble.com/Tab-Completion-Trunk-tp4029755p4029763.html

Sent from the Karaf - Dev mailing list archive at Nabble.com.






--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com



Re: Tab Completion Trunk

2013-09-27 Thread nseb
+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.


Re: Support Assembly protocol

2013-09-27 Thread nseb
Up my patch , to support assembly protocol in feature.xml , very very useful
in development mode



--
View this message in context: 
http://karaf.922171.n3.nabble.com/Support-Assembly-protocol-tp4029163p4029769.html
Sent from the Karaf - Dev mailing list archive at Nabble.com.


Re: Tab Completion Trunk

2013-09-27 Thread Achim Nierbeck
+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_nicoul...@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.




-- 

Apache Karaf http://karaf.apache.org/ Committer  PMC
OPS4J Pax Web http://wiki.ops4j.org/display/paxweb/Pax+Web/ Committer 
Project Lead
OPS4J Pax for Vaadin http://team.ops4j.org/wiki/display/PAXVAADIN/Home
Commiter  Project Lead
blog http://notizblog.nierbeck.de/