Re: Filtering for effort in org-agenda

[Bernt Hansen <bernt@norang.ca>]

Carsten Dominik <carsten.dominik@gmail.com> writes:

> On Mar 30, 2009, at 8:01 PM, Matthew Lundin wrote:
>
>>
>> A quick question. Sometimes during the day, when my effort is
>> flagging,
>> I like to see all items that have an effort of, say, < 0:10, so I
>> can do
>> a bunch of quick tasks in succession. When I apply the agenda filter
>> ( /
>> < 0:10 ), however, the resulting list includes all items that do not
>> have a
>> defined effort. Would it be possible to create an option to exclude
>> items where effort is nil from the filtered list?
>>
>> I had a quick look at org-agenda-compare-effort in org-agenda.el (line
>> 4734), and if I'm reading the function correctly, it gives items
>> without
>> a defined effort the value of 0. Is this correct?
>
> Correct.
>
> I guess we could define a variable to put a different default or so.
> Or we could apply org-sort-agenda-noeffort-is-high also in this case
> and supply a large number instead of 0.
>
> - Carsten
>
>>
>> Any advice would be greatly appreciated.

I think I changed that behaviour originally in commit dc43885

I was looking for a way to select tasks with no effort so I could define
an effort before working on them.

I'd like to retain the ability to find tasks with no effort easily.
There's probably a better solution that the one I came up with.

-Bernt


------------------------------------------------------------------------
commit dc438851021ba340bbff3462671e2b142ff6bdbf
Author: Carsten Dominik <carsten.dominik@gmail.com>
Date:   Tue Nov 11 06:56:32 2008 +0100

    Treat no effort defined as 0 minutes.
    
    Bernt Hanses writes:
    
    This changes the default value for Effort during agenda filtering so
    that an undefined Effort value is treated as 0 instead of nil.  Tasks
    with no effort defined now return zero effort when selecting tasks for
    the filter.
    
    There was effectively no way to select 'tasks with no effort defined'
    using the agenda effort filter.  The '<' operator is interpreted as
    '<=' and the default effort selection defined in
    org-agenda-filter-by-tag starts with zero ("0 0:10 ...") so this
    change just treats tasks with no effort defined the same as tasks with
    an effort of 0.
    
    This allows fast selection of NEXT tasks with no effort defined.
    Column view with follow-mode active in the agenda is great for quickly
    filling in the agenda estimated effort values for tasks.  Just display
    your Next tasks, then / 0 to select tasks with no effort and enter
    column mode (C-c C-x C-c) and fill in your effort values with the
    quick keys (0-9) for all of the tasks that have blanks in the effort
    column.
------------------------------------------------------------------------