[Ml-yokadi] feature request
Aurélien Gâteau
aurelien.gateau at free.fr
Thu Jul 23 14:05:19 CEST 2009
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.
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.
> - 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.
>
>>> By the way, filtering t_list with keywords raise a bug in dynamic width
>>> output that I introduce the 9th of July with commit cd93bae1ce6e3325. The
>>> width is not properly computed when t_list is filtered with keyword (too
>>> short). This bug can already be triggered by simply doing t_list @foo
>> I worked a bit on a related bug: I made sure there is enough room to
>> display the "*" suffix (see latest commits).
>>
>> I have an idea to fix that bug, but I am not done yet.
>
> I did not start to investigate but it's on the top of my annoying bug list
> ;-). Now it has the @aga keyword meaning you're working on it :-)
Hehe :)
Aurélien
More information about the Ml-yokadi
mailing list