From: William Gardella <gardellawg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: clocking ongoing items
Date: Fri, 14 Dec 2012 02:50:53 -0500 [thread overview]
Message-ID: <87ehitqdgi.fsf@gmail.com> (raw)
In-Reply-To: 50CACC76.9060002@online.de
Hi Rainer,
Rainer Stengele <rainer.stengele-BGeptl67XyCzQB+pC5nmwQ@public.gmane.org> writes:
> Hi all!
>
> I wonder how others are clocking ongoing isues, which are not really
> todos but more like "issues" collecting clocked time for work done
> regularly. Example: Reading mail and organising daily priorities of
> tasks. This "todo" will not finish very soon. I want this item to be
> clocked daily but do not want it to look like a standard todo. How do
> others handle this? I remember Bernt once had a tag "ONGOING" which he
> dropped again.
>
> Cheers,
> Rainer
>
>
>
Your use case sounds like a good fit for the `org-habit' module. See
(info "(org) Tracking your habits"). A habit is like a periodic TODO
which you mark DONE each time you complete it for the day, but it resets
itself to being "undone" again after an interval of time passes. Habits
also come with a nice display in agenda views to show you how often you
actually do something. (I use this feature to track my daily meditation
habits, for example). This way, together with org's time clock, the
task is periodic, but the clock times and relevant notes can still all
be kept in one place and the task can be represented as a single
headline.
Best,
--
WGG
I use grml (http://grml.org/)
next prev parent reply other threads:[~2012-12-14 7:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 6:51 clocking ongoing items Rainer Stengele
2012-12-14 7:26 ` Brian van den Broek
2012-12-14 7:50 ` William Gardella [this message]
2012-12-14 10:53 ` Memnon Anon
2012-12-14 15:47 ` Rainer Stengele
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ehitqdgi.fsf@gmail.com \
--to=gardellawg-re5jqeeqqe8avxtiumwx3w@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.