From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Sebastien Vauban" Subject: Re: Bug: org-time-stamp loses repeater interval Date: Wed, 29 Jun 2011 09:28:24 +0200 Message-ID: <80sjqtdrl3.fsf@somewhere.org> References: <2011-06-24T16-30-43@devnull.Karl-Voit.at> <8772.1308931315@alphaville.dokosmarshall.org> <2011-06-26T13-23-38@devnull.Karl-Voit.at> <8739ivw8e8.fsf@gnu.org> <2011-06-28T15-28-18@devnull.Karl-Voit.at> <2011-06-28T18-04-12@devnull.Karl-Voit.at> <87sjqt6f3i.fsf@gnu.org> <2011-06-28T20-40-40@devnull.Karl-Voit.at> <874o39v9td.fsf@gnu.org> <24271.1309302652@alphaville.americas.hpqcorp.net> <87pqlxjyp9.fsf@gnu.org> <5383.1309311845@alphaville.dokosmarshall.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org To: emacs-orgmode-mXXj517/zsQ@public.gmane.org Hi Nick, Nick Dokos wrote: > Bastien wrote: >> Okay, I've pushed another fix. >> >> This let me stumble upon another case: the one with org-schedule and >> org-deadline ignoring warning cookies -- these cases are also fixed. >> >> Please confirm! > > Confirmed. There is a peculiar corner case: > > If I have a headline that's both scheduled and deadlined, like this: > > * scheduled > DEADLINE: <2011-07-04 Mon +2w -3d> > SCHEDULED: <2011-07-06 Wed +1w -2d> > > and I C-c C-s in the scheduled date, I get a second SCHEDULED: item > with the new date on the DEADLINE line. The original SCHEDULED: is > still on the next line, unchanged - like this: > > * scheduled > DEADLINE: <2011-07-04 Mon +2w -3d> SCHEDULED: <2011-07-03 Sun +1w -2d> > SCHEDULED: <2011-07-06 Wed +1w -2d> See http://www.mail-archive.com/emacs-orgmode-mXXj517/zsQ@public.gmane.org/msg37987.html where I report such a case with inactive timestamps and SCHEDULED dates. See Bastien's answer in the same thread. In this case, SCHEDULED should come first, before DEADLINE, for it to work. Note -- I prefer that order (SCHEDULED, then DEADLINE) since dates are then chronologically sorted (at least, I expect so, that SCHEDULED date < DEADLINE date)... Best regards, Seb -- Sebastien Vauban