From: Detlef Steuer <detlef.steuer@gmx.de>
To: emacs-orgmode@gnu.org
Subject: Re: Non-scheduled repeating tasks
Date: Wed, 7 May 2014 15:56:07 +0200 [thread overview]
Message-ID: <20140507155607.58a4f538@gaia> (raw)
In-Reply-To: CAH1=Abipz6qsJ1+9Q2TgpnDPU44c=CEik50v6WdZYp+HBfCVaw@mail.gmail.com
Am Mon, 5 May 2014 15:52:26 +0200
schrieb Albin Stjerna <albin.stjerna@gmail.com>:
> Hi,
>
> I've been thinking about how to integrate tasks which are to some
> extent tracked elsewhere into my org-mode workflow, such as for
> example "read N chapter of book A" or "watch K video lectures at X".
>
> I'd like a way to describe in org-mode that a task should be completed
> a number of times, and then have org-mode let the task recur a number
> of times, possibly with a cool-down period (but that's not really
> necessary). The normal progress cookies % and / would preferrably be
> used to indicate progress in the TODO headings themselves.
>
Not sure if I understand correctly, but did you look into org-habits?
Sounds similar.
http://orgmode.org/manual/Tracking-your-habits.html
Detlef
> 1. Has something like this been attempted by anyone else before?
> 2. Which org-mode hooks would be a good place to start integrating
> something that would both potentially block TODO transitions and have
> to read/write properties and/or special drawers in org-mode? At first,
> I thought that the problem could be trivially solved with the
> org-blocker-hook, but I realised that it said it shouldn't update the
> org buffers, and my function needs to in order to update the state for
> blocked tasks (e.g. increment the counter).
>
> Thanks in advance!
> Albin
>
>
next prev parent reply other threads:[~2014-05-07 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 13:52 Non-scheduled repeating tasks Albin Stjerna
2014-05-07 13:56 ` Detlef Steuer [this message]
2014-05-23 5:52 ` Bastien
2014-05-23 12:15 ` Albin Stjerna
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=20140507155607.58a4f538@gaia \
--to=detlef.steuer@gmx.de \
--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).