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

[Karl Voit]

I checked out via «git pull», re-compiled Org-mode and tested again:
this time, all my test cases mentioned in the original posting
worked fine. Bug fixed so far.

* Nick Dokos <address@hidden> wrote:
>
> There is a peculiar corner case:
>
> If I have a headline that's both scheduled and deadlined, like this:
>
> --8<---------------cut here---------------start------------->8---
> * scheduled 
>   DEADLINE: <2011-07-04 Mon +2w -3d>
>   SCHEDULED: <2011-07-06 Wed +1w -2d>
> --8<---------------cut here---------------end--------------->8---
>
> 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:
>
> --8<---------------cut here---------------start------------->8---
> * scheduled 
>   DEADLINE: <2011-07-04 Mon +2w -3d> SCHEDULED: <2011-07-03 Sun +1w -2d>
>   SCHEDULED: <2011-07-06 Wed +1w -2d>
> --8<---------------cut here---------------end--------------->8---

I can confirm this behavior at my side too.

But: When I create SCHEDULED (and DEADLINE) using the shortcut «C-c
C-s» SCHEDULED is always in the same like as DEADLINE. In this case,
I can not notice the behavior as above. The behavior described by
Nick happens only (here) if SCHEDULED is not in the same like as
DEADLINE.

Remark regarding the order of the two entries: the last thing that
gets added/modified is always the last one in this line. So if I
create SCHEDULED and DEADLINE, DEADLINE is the second (last) in the
line. When I modify SCHEDULED afterwards, it is SCHEDULED that gets
positioned at the end of the line. Same for modifications of
DEADLINE.

-- 
Karl Voit