Re: [O] Bug: org-time-stamp loses repeater interval

[Sebastien Vauban]

Hi Nick,

Nick Dokos wrote:
> Bastien <address@hidden> 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/address@hidden/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