[Ml-yokadi] feature request

[Sébastien Renard]

Le jeudi 23 juillet 2009 14:05:19, Aurélien Gâteau a écrit :
> Sébastien Renard wrote:
> > Le jeudi 23 juillet 2009 10:27:02, Aurélien Gâteau a écrit :
> >> What do you think about my suggestion to group by the first argument?
> >> "t_list @foo%" would group by keywords starting with "foo", "t_list
> >> prj%" would group by projects starting with "prj".
> >
> > It has some drawbacks :
> > - with t_list -k myproject I can display just my project task grouped by
> > keywords. How could be have this behaviour with your proposition ?
>
> With my proposition you could do "t_list @foo% myproject" to list all
> tasks from myproject, grouped by keywords matching "@foo%". If you
> wanted to list all tasks with one group per keyword, I think "t_list @%
> myproject" would work.

For once you defend the magic point of view (arg order) and I would prefer 
explicit (the -k switch).
I have to think about it.

We could do both (without switch arg order is used).

> Having the ability to specify a matching expression for keywords makes
> it easier to do intelligent grouping if you organise your keywords in a
> hierarchy. As I said before, you could group tasks by people with
> "t_list @people%" for example. I think this would fit David use case
> better.

We need that. Definitely. I will propose a patch for that in few days.

> > - I can't display all tasks grouped by keyword without a -k switch.
>
> You mean the equivalent of t_list with no parameters? Would this be
> really useful? Once you have many tasks, listing them without a criteria
>  is useless I think.

It's a matter of choice. Default to project or keyword grouping ? Default to 
project is a sensible choice, but a switch to choose keyword grouping is not 
so bad.

a+
-- 
Sébastien