james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benoit Tellier <be...@minet.net>
Subject Re: James CLI is unreadable
Date Wed, 16 Dec 2015 08:38:18 GMT
Hi,

@matthieu : we can make commands case insensitive.

@aduprat : completion seems hard to achive but maybe we can think of
supporting partial unambiguous commands... What do you think of it ?

We can add a ./james-cli.sh help command

What do you want by "better result presentation"?

I'll open the jira.

Le 16/12/2015 09:07, Antoine DUPRAT a écrit :
> Hello,
> 
> It seems to be a good idea.
> 
> May be it's also the time to investigate on a tool providing us
> additional features to the cli:
> - completion
> - help
> - better result presentation
> - ...
> 
> Antoine
> 
>> Hi,
>>
>> Today I want to raise an issue :
>>
>>   - It is nearly impossible to read James CLI help message
>>   - James CLI command line naming is obscure, too long and too monolitic
>>
>> Having a lot of commands does not seem bad to me, but they should be
>> organised better than just grouped all together.
>>
>>
>>
>> I think something like :
>>
>> james-cli.sh DOMAIN ADD toto.org
>> james-cli.sh DOMAIN LIST
>> james-cli.sh DOMAIN REMOVE
>>
>> will be better than
>>
>> james-cli.sh ADDDOMAIN toto.org
>> james-cli.sh LISTDOMAIN
>> james-cli.sh REMOVEDOMAIN toto.org
>>
>> It will get even better with "cryptic" commands like :
>>
>> james-cli.sh ADDADDRESSMAPPING user domain fromAddress
>>
>> would be :
>>
>> james-cli.sh MAPPING ADDRESS ADD user domain fromAddress
>>
>> The global syntax I propose is :
>>
>> james-cli.sh FUNCTIONNALITY [EXTRA SPECS...] COMMAND [ARGS... ]
>>
>>
>>
>> On the help display it might help as :
>>
>>   - Related commands will be grouped together, CLRF isolated from other
>> groups
>>   - We can add a help message to explain the functionality
>>   - As they are space separated, command names will get easier to read
>>
>>
>> If peoples thinks this might help, I am motivated to :
>>
>>   - 1/ open a jira issue
>>   - 2/ code this up (this seems not that complicated)
>>
>> And of course, if you have feedbacks, you will be very welcome.
>>
>> Benoit
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
>> For additional commands, e-mail: server-dev-help@james.apache.org
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Mime
View raw message