From: "N. Raghavendra" <nyraghu27132@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Repeated tasks
Date: Mon, 16 May 2016 23:43:31 +0530 [thread overview]
Message-ID: <m2zirpan1w.fsf@hydra.local> (raw)
In-Reply-To: <87shxlpvq9.fsf@tricheco.cybervalley.org> (Leandro Noferini's message of "Fri, 13 May 2016 22:07:58 +0200")
At 2016-05-13T22:07:58+02:00, Leandro Noferini wrote:
> "N. Raghavendra" <raghu@hri.res.in> writes:
>
>> Is there a way to specify the timestamp for a repeated task which has
>> to be done on the second Sunday of every month? I'd like the todo
>> state of the task to go back to TODO after it has been marked DONE, as
>> described in the section on repeated tasks in the Org manual.
>
> You can use sexp expressions: look at the chapter 8.3 of the manual, 8.3
> Deadlines and scheduling
>
> For example I use this expression for the first sunday of every month:
>
> <%%(diary-float t 0 1)>
Thanks for the reply. Yes, I know this diary-sexp, but the trouble with
it is that after I change the state of such a task to DONE, it remains
DONE. What I want is that when I change the state to DONE, the task
must be rescheduled for the second Sunday of the next month, and the
state reverted to TODO. This will be like the repeated task
functionality described in the manual.
Cheers,
Raghu.
--
N. Raghavendra <raghu@hri.res.in>, http://www.retrotexts.net/
Harish-Chandra Research Institute, http://www.hri.res.in/
next prev parent reply other threads:[~2016-05-16 18:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 5:16 Repeated tasks N. Raghavendra
2016-05-13 20:07 ` Leandro Noferini
2016-05-16 18:13 ` N. Raghavendra [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-13 4:51 N. Raghavendra
2016-05-13 4:39 N. Raghavendra
2016-05-13 2:56 N. Raghavendra
2016-05-12 20:11 N. Raghavendra
2009-09-01 15:03 Repeated Tasks Noorul Islam
2009-09-01 15:15 ` Sebastian Rose
2009-09-01 17:56 ` Noorul Islam
2009-04-11 5:10 Antano Solar John
2009-04-12 3:13 ` Matthew Lundin
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=m2zirpan1w.fsf@hydra.local \
--to=nyraghu27132@gmail.com \
--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 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.