emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Albin Stjerna <albin.stjerna@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Non-scheduled repeating tasks
Date: Fri, 23 May 2014 07:52:44 +0200	[thread overview]
Message-ID: <87sio1f3df.fsf@bzg.ath.cx> (raw)
In-Reply-To: <CAH1=Abipz6qsJ1+9Q2TgpnDPU44c=CEik50v6WdZYp+HBfCVaw@mail.gmail.com> (Albin Stjerna's message of "Mon, 5 May 2014 15:52:26 +0200")

Hi Albin,

Albin Stjerna <albin.stjerna@gmail.com> writes:

> 1. Has something like this been attempted by anyone else before?

No -- but there are regular feature requests around making repeaters
more flexible.  I hope I can enhance this for 8.4 (or 9.0.)

> 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?

You can cook something from `org-after-todo-state-change-hook'.

Put the repeat value in a property, decrease it each time a task is
done until the repeater value is 0.  Displaying the repeater value can
be done in column mode.

That's for the first part of this feature -- the one with blocking
TODOs, see `org-blocker-hook' and `org-trigger-hook'.  Not sure it
will help though.

See also the manual on adding properties (i.e. `org-entry-put') and
hacking Org in general.



  parent reply	other threads:[~2014-05-23  5:53 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
2014-05-23  5:52 ` Bastien [this message]
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:

  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=87sio1f3df.fsf@bzg.ath.cx \
    --to=bzg@gnu.org \
    --cc=albin.stjerna@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).