[Ml-yokadi] Request for change t_list -t behaviour

Sébastien Renard Sebastien.Renard at digitalfox.org
Wed Oct 7 15:30:58 CEST 2009


Le mardi 6 octobre 2009 09:09:10, Aurélien Gâteau a écrit :
> (Sorry about late answer, I am a father for the 2nd time!)

Congratulations !

> Sébastien Renard a écrit :
> > Le mercredi 30 septembre 2009 13:52:24, Aurélien Gâteau a écrit :
> >> I would rather add a long option only first, then find a short option
> >> after using it for a while, if we find out we use it a lot.
> >
> > Why not just keep -t as we have now ?
>
> "-t" does not sound like a shortcut for "overdue". Furthermore, it would
> change the existing option behavior, this sounds like a bad thing to do
> to users (even if I agree it is not the most used option)

Ok, so let's add a *new* option for overdue tasks and remove or deprecate old 
-t option ?

> >> I believe we went a bit wild in the beginning and allocated too many
> >> short options. Using long options could be made more user friendly if we
> >> had completion on options
> >
> > Sure, it is a very good idea !
>
> I gave it a try, but it's not as simple as I expected, because readline
> does not return the correct begidx value for completion if the completed
> word starts with "-". Need to investigate.

readline completion is often quite painful to debug...

> >> and a display of the help message when using
> >> an unknown option.
> >
> > For now this is silently ignored to allow user to make something like the
> > following without the hassle of escaping :
> > bug_add my_project why the hell option --foo and -b do not work ?
>
> Good point, but this is probably not relevant for t_list.

Exact. This is a general YokadiParser mechanism. If you feel this is very 
important we could add an option to YokadiOptionParser to deactivate or not 
ignoring unknown option.

a+
-- 
Sébastien


More information about the Ml-yokadi mailing list