From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Lundin Subject: Re: Bug: org-auto-repeat-maybe only updates first timestamp [7.01trans] Date: Fri, 17 Sep 2010 08:05:23 -0400 Message-ID: <87pqwc4lto.fsf@fastmail.fm> References: <24331.1284476463@iu.edu> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from [140.186.70.92] (port=50957 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OwZpK-0002nl-VI for emacs-orgmode@gnu.org; Fri, 17 Sep 2010 08:14:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OwZh6-0007M9-VD for emacs-orgmode@gnu.org; Fri, 17 Sep 2010 08:05:34 -0400 Received: from out2.smtp.messagingengine.com ([66.111.4.26]:56992) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OwZh6-0007Kl-T1 for emacs-orgmode@gnu.org; Fri, 17 Sep 2010 08:05:32 -0400 In-Reply-To: <24331.1284476463@iu.edu> (Andrew J. Korty's message of "Tue, 14 Sep 2010 11:01:03 -0400") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: "Andrew J. Korty" Cc: emacs-orgmode@gnu.org "Andrew J. Korty" 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