From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: org-dblock-write:count
Date: Fri, 14 Feb 2014 13:42:54 +0100 [thread overview]
Message-ID: <86mwhtj25t.fsf@somewhere.org> (raw)
In-Reply-To: 8638jruwhp.fsf@somewhere.org
"Sebastien Vauban" wrote:
> Adam Spiers wrote:
>> I just had an awesome conversation with Sacha about more effective
>> daily/weekly reviewing with org-mode :-) One of the things we talked
>> about was quantifying the number of tasks (TODO keywords) in any given
>> state, as a means of becoming more aware of your progress over time.
>> I have had some success in the past using the "measure what you want
>> to manage maxim"[1], and wanted to start applying this to my horribly
>> massive TODO.org file.
>>
>> #+BEGIN:dynamic block
>> #+BEGIN: count :keywords (\"NEXT\" \"DONE\") :searches (\"@phone\" \"@home\")
>> | NEXT | 522 |
>> | DONE | 69 |
>> | @phone | 77 |
>> | @home | 182 |
>> #+END:
>
> To me, the best thing would be to see that count up-to-date with every
> custom agenda view.
>
> See http://lists.gnu.org/archive/html/emacs-orgmode/2013-09/msg01075.html
> for a patch I proposed in that direction.
>
> However, I had some comments of Bernt saying that some edge cases are
> not covered (when the block separator is empty). I still have to fix
> that, and come back with a fully working solution.
An alternative could be `org-effectiveness', and having a hook to
display the count (in the mode line) at each opening of an Org file...
Best regards,
Seb
--
Sebastien Vauban
prev parent reply other threads:[~2014-02-14 12:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-09 13:03 org-dblock-write:count Adam Spiers
2014-02-10 9:50 ` org-dblock-write:count Sebastien Vauban
2014-02-14 12:42 ` Sebastien Vauban [this message]
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=86mwhtj25t.fsf@somewhere.org \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).