From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Andrew J. Korty" <ajk@iu.edu>
Subject: Re: Bug: org-auto-repeat-maybe only updates first timestamp
 [7.01trans]
Date: Thu, 16 Sep 2010 10:58:45 -0400
Message-ID: <40096.1284649125@iu.edu>
References: <24331.1284476463@iu.edu> <878w32c8rq.fsf@gollum.intra.norang.ca>
Content-Type: text/plain; charset=utf-8; format=flowed
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from [140.186.70.92] (port=44035 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OwGF1-0005o0-3W
	for emacs-orgmode@gnu.org; Thu, 16 Sep 2010 11:19:28 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <ajk@iu.edu>) id 1OwFvC-00083T-Tm
	for emacs-orgmode@gnu.org; Thu, 16 Sep 2010 10:59:00 -0400
Received: from singsing.itso.iu.edu ([149.166.143.49]:40395)
	by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from <ajk@iu.edu>)
	id 1OwFvC-00083G-Qv
	for emacs-orgmode@gnu.org; Thu, 16 Sep 2010 10:58:46 -0400
Received: from iu.edu (149-166-143-228.dhcp-in.iupui.edu [149.166.143.228])
	by singsing.itso.iu.edu (Postfix) with ESMTPA id 50265239242
	for <emacs-orgmode@gnu.org>; Thu, 16 Sep 2010 14:58:19 +0000 (UTC)
In-reply-to: <878w32c8rq.fsf@gollum.intra.norang.ca>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=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: emacs-orgmode@gnu.org

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