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:29:05 -0400 Message-ID: <87iq244kq6.fsf@fastmail.fm> References: <24331.1284476463@iu.edu> <878w32c8rq.fsf@gollum.intra.norang.ca> <40096.1284649125@iu.edu> <40246.1284650926@iu.edu> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from [140.186.70.92] (port=40931 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Owa3w-0004d1-V2 for emacs-orgmode@gnu.org; Fri, 17 Sep 2010 08:29:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Owa3v-0003D2-Dl for emacs-orgmode@gnu.org; Fri, 17 Sep 2010 08:29:08 -0400 Received: from out2.smtp.messagingengine.com ([66.111.4.26]:41830) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Owa3v-0003Cy-9n for emacs-orgmode@gnu.org; Fri, 17 Sep 2010 08:29:07 -0400 In-Reply-To: <40246.1284650926@iu.edu> (Andrew J. Korty's message of "Thu, 16 Sep 2010 11:28:46 -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: Bernt Hansen , emacs-orgmode@gnu.org "Andrew J. Korty" writes: > Andrew J. Korty wrote: > >> Bernt Hansen 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 ... > > Oops, frobbing org-agenda-ignore-deadlines won't help. It works in > the case of driver's license renewal, but it breaks a different case. > Say I've been asked to review a document by October 31. So I set a > deadline of 2010-12-31. But I do want to see it on my tags-todo list > now because if I had time now, I could review the documents and submit > my comments well before the deadline. I assume you mean org-agenda-todo-ignore-deadlines. In this particular case you could set that variable to 'far, which causes deadlines to be displayed only when they fall within the lead time specified in org-agenda-warning days or (as in the example above) in the timestamp itself. Here's an example: --8<---------------cut here---------------start------------->8--- * TODO Review really important document DEADLINE: <2010-10-31 Sun -2m> * TODO Review less important document DEADLINE: <2010-10-31 Sun> --8<---------------cut here---------------end--------------->8--- Let's assume the following settings: --8<---------------cut here---------------start------------->8--- (setq org-agenda-todo-ignore-deadlines 'far org-deadline-warning-days 14) --8<---------------cut here---------------end--------------->8--- With these settings, the first task would show up *today* both in your agenda and in your TODO list, while the second task would appear in both places two weeks before the deadline. That said, I sometimes set both a scheduled and deadline timestamp to create an extra reminder/safety net, so the original bug you reported is certainly an issue. Best, Matt