emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt Lundin <mdl@imapmail.org>
To: "Andrew J. Korty" <ajk@iu.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: org-auto-repeat-maybe only updates first timestamp [7.01trans]
Date: Fri, 17 Sep 2010 08:05:23 -0400	[thread overview]
Message-ID: <87pqwc4lto.fsf@fastmail.fm> (raw)
In-Reply-To: <24331.1284476463@iu.edu> (Andrew J. Korty's message of "Tue, 14 Sep 2010 11:01:03 -0400")

"Andrew J. Korty" <ajk@iu.edu> writes:

> Remember to cover the basics, that is, what you expected to happen and
> what in fact did happen.  You don't know how to make a good report?  See
>
>     http://orgmode.org/manual/Feedback.html#Feedback
>
> Your bug report will be posted to the Org-mode mailing list.
> ------------------------------------------------------------------------
>
> 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>

I can confirm this bug, although AFAICT it occurs only when both the
SCHEDULED and DEADLINE repeating syntax are of the "++" variety.

E.g.,

The example above results in:

--8<---------------cut here---------------start------------->8---
* TODO do something by Sunday but not until Friday
  SCHEDULED: <2010-09-24 Fri ++1w> DEADLINE: <2010-09-19 Sun ++1w>
--8<---------------cut here---------------end--------------->8---

However, if the scheduled timestamp is not a "double plus" (++), then
the timestamps advance as expected:

--8<---------------cut here---------------start------------->8---
* TODO Another example
  SCHEDULED: <2010-09-17 Fri +1w> DEADLINE: <2010-09-19 Sun ++1w>
--8<---------------cut here---------------end--------------->8---

becomes...

--8<---------------cut here---------------start------------->8---
* TODO Another example
  SCHEDULED: <2010-09-24 Fri +1w> DEADLINE: <2010-09-26 Sun ++1w>
--8<---------------cut here---------------end--------------->8---

Other combinations also work as expected:

--8<---------------cut here---------------start------------->8---
* TODO Another example
  SCHEDULED: <2010-09-17 Fri .+1w> DEADLINE: <2010-09-19 Sun .+1w>
--8<---------------cut here---------------end--------------->8---

becomes...

--8<---------------cut here---------------start------------->8---
* TODO Another example
  SCHEDULED: <2010-09-24 Fri .+1w> DEADLINE: <2010-09-24 Fri .+1w>
--8<---------------cut here---------------end--------------->8---

Best,
Matt

  parent reply	other threads:[~2010-09-17 12:14 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
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 [this message]
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=87pqwc4lto.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --cc=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).