From: Carsten Dominik <carsten.dominik@gmail.com>
To: Bernt Hansen <bernt@norang.ca>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Filtering for effort in org-agenda
Date: Tue, 31 Mar 2009 15:20:39 +0200 [thread overview]
Message-ID: <6A61D6DF-501B-422A-BBBE-D57382792201@gmail.com> (raw)
In-Reply-To: <87iqlp3mxx.fsf@gollum.intra.norang.ca>
On Mar 31, 2009, at 2:18 PM, Bernt Hansen wrote:
> Carsten Dominik <carsten.dominik@gmail.com> writes:
>
>> On Mar 30, 2009, at 10:37 PM, Bernt Hansen wrote:
>>>
>>> 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.
>>
>> Are you doing this now using filtering for effort, or a property
>> search for Effort?
>
> I'm using filtering for effort.
>
> I'm doing this from the agenda currently - getting a list of todo
> tasks,
> limiting to tasks with tag NEXT and then further limiting it to effort
> times <0 using the standard agenda effort filter
>
>
> List of all TODO entries (excluding dated items)
> / Limit to NEXT tagged tasks
> / / Limit to effort <= 0
> / / /
> C-c a t / N / + 1
You are now using "1" and have your first effort etimate set to zero
minutes.
I guess we could make "0" a special selection, not for the 10th effort
step, but for no effort defined. Would that make sense?
- Carsten
>
> -Bernt
>
>>
>> - Carsten
>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>> 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.
>>> ------------------------------------------------------------------------
next prev parent reply other threads:[~2009-03-31 13:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 18:01 Filtering for effort in org-agenda Matthew Lundin
2009-03-30 18:29 ` Carsten Dominik
2009-03-30 20:37 ` Bernt Hansen
2009-03-31 11:38 ` Carsten Dominik
2009-03-31 12:18 ` Bernt Hansen
2009-03-31 13:20 ` Carsten Dominik [this message]
2009-03-31 13:22 ` Bernt Hansen
2009-03-31 18:12 ` Carsten Dominik
2009-03-31 22:05 ` Matthew Lundin
2009-03-30 18:57 ` Nick Dokos
2009-03-30 19:20 ` Nick Dokos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6A61D6DF-501B-422A-BBBE-D57382792201@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).