From: "Andrew J. Korty" <ajk@iu.edu>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: org-auto-repeat-maybe only updates first timestamp [7.01trans]
Date: Thu, 16 Sep 2010 10:58:45 -0400 [thread overview]
Message-ID: <40096.1284649125@iu.edu> (raw)
In-Reply-To: <878w32c8rq.fsf@gollum.intra.norang.ca>
Bernt Hansen <bernt@norang.ca> wrote:
> > If I have multiple timestamps in a TODO item, org-auto-repeat-maybe
> > only advances the first one. In the following example, I'd like both
> > the SCHEDULED and DEADLINE timestamps to advance when the item is
> > marked DONE, but only the SCHEDULED timestamp advances.
> >
> > * TODO do something by Sunday but not until Friday
> > SCHEDULED: <2010-09-17 Fri ++1w> DEADLINE: <2010-09-19 Sun ++1w>
>
> Why not just drop the SCHEDULED: tag and change the DEADLINE task to
>
> DEADLINE: <2010-09-19 Sun ++1w -2d>
>
> This way it won't show up in your agenda until Friday -- 2 days before
> it's due.
Right, but then it will show up in tags-todo lists before I want it
to. An example is renewing my driver's license, for which I could use
DEADLINE: <2011-10-12 Wed ++4y -2w>
but it would show up in tags-todo lists way before it would make sense
to renew. Although I suppose I could set org-agenda-ignore-deadlines
to 'all and just rely on the daily/weekly agenda to show them to me ...
ajk
next prev parent reply other threads:[~2010-09-16 15:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-14 15:01 Bug: org-auto-repeat-maybe only updates first timestamp [7.01trans] Andrew J. Korty
2010-09-16 9:55 ` Bernt Hansen
2010-09-16 14:58 ` Andrew J. Korty [this message]
2010-09-16 15:28 ` Andrew J. Korty
2010-09-17 12:29 ` Matt Lundin
2010-09-17 12:48 ` Andrew J. Korty
2010-09-17 18:47 ` Matt Lundin
2010-09-17 21:34 ` Andrew J. Korty
2010-09-18 2:39 ` Matt Lundin
2010-09-18 13:08 ` Andrew J. Korty
2010-09-17 12:05 ` Matt Lundin
2010-09-17 12:43 ` Andrew J. Korty
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=40096.1284649125@iu.edu \
--to=ajk@iu.edu \
--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).