From: Bernt Hansen <bernt@norang.ca>
To: John Hendy <jw.hendy@gmail.com>
Cc: c b <24x7x366@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Org-mode repeating tasks issue
Date: Mon, 21 May 2012 09:06:26 -0400 [thread overview]
Message-ID: <87fwat4ral.fsf@norang.ca> (raw)
In-Reply-To: <CA+M2ft8gUumLpaD3g0ecj1WvcfRwDzGn5eR2D1Y34-ksE-bymA@mail.gmail.com> (John Hendy's message of "Sun, 20 May 2012 08:33:09 -0500")
John Hendy <jw.hendy@gmail.com> writes:
> On Sat, May 19, 2012 at 7:41 PM, c b <24x7x366@gmail.com> wrote:
>>
>> Hi,
>>
>> I have been using org-mode with emacs(23) for about a year now and love it.
>>
>> However, sometime in the last couple of weeks, I did a git pull on the master branch (and I redid the same today) and noticed that my recurring tasks are broken.
>>
>> E.g.
>>
>> I have a task
>>
>> ** TODO Pay Creditcard bill
>> DEADLINE: <2012-05-15 Tue +1m -7d>
>>
>> and when I marked it done, it changed state to DONE
>> ** DONE Pay Creditcard bill
>> CLOSED: [2012-05-18 Fri 22:13] DEADLINE: <2012-05-15 Tue +1m -7d>
>>
>>
>> I have been trying to figure out what went wrong, but am clueless. Any pointers on what might be wrong, would be appreaciated.
>>
>
> I don't use this much, but have been contemplating it and thus the
> various org-mode pages on repeating tasks are somewhat fresh in my
> head. Here was my initial thought:
>
> - The org-mode manual itself on repeated tasks does not mention that
> kind of repeating task syntax
> --- http://orgmode.org/manual/Repeated-tasks.html#Repeated-tasks
> --- Only +1, ++1, and .+1 are discussed
>
> - The /org-habit/ page, on the other hand, does mention such syntax
> (well, kind of)
> --- http://orgmode.org/manual/Tracking-your-habits.html
> --- Note that this page uses .+2d/4d syntax
>
> Anyway, I very likely missed something, but I can't find the specific
> syntax you're looking for in the manual sections above. If the
> functionality of org-habit /does/ do what you want, perhaps you could
> switch to that? If you use this syntax widely, that could be a pain.
>
> Let me know what you think? Also, please point to the documentation
> illustrating the +1m -7d usage. I'd like to see it as well as I'm
> curious about the various time stamp options.
>
DEADLINE: <2012-05-15 Tue -7d>
is a standard deadline with a 7 day warning period as defined in section
8.3 Deadlines and scheduling.
DEADLINE: <2012-05-15 Tue +1m -7d>
This just adds a monthly repeater to the syntax and is perfectly legal
syntax AFAIK.
This entry repeats normally for me.
Org-mode version 7.8.10 (release_7.8.10-578-g42f7ba @ /home/bernt/git/org-mode/lisp/)
GNU Emacs 23.2.1 (i486-pc-linux-gnu, GTK+ Version 2.20.0) of 2010-12-11 on raven, modified by Debian
Regards,
Bernt
next prev parent reply other threads:[~2012-05-21 13:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-20 0:41 Org-mode repeating tasks issue c b
2012-05-20 13:33 ` John Hendy
2012-05-21 13:06 ` Bernt Hansen [this message]
2012-05-26 0:46 ` c b
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=87fwat4ral.fsf@norang.ca \
--to=bernt@norang.ca \
--cc=24x7x366@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jw.hendy@gmail.com \
/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).