* Bastien <b...@altern.org> wrote: > Karl Voit <devn...@karl-voit.at> writes: > >> Same to me. Unfortunately I am using timestamps not only in the >> context of DEADLINE or SCHEDULED but also for events that should >> simply show up on the agenda (without deadline or scheduled >> timestamp at all). >> >> To me this *is* a bug since my expected behavior of org-time-stamp >> to modify an existing timestamp is different. > > It is now fixed in the latest git version. Please test and report, > if possible.
I checked out d7c693c1ffe2ebf38604dd30fdd2f9d51a1c44d0 which should fix the problem and tested with «Emacs 23.2.1 (i686-pc-linux-gnu, GTK+ Version 2.24.4) of 2011-04-04 on rothera, modified by Debian» and «Org-mode version 7.5 (release_7.5.462.gd7c69)» created timestamp with «C-c .» <2011-06-28 Tue> modified with «C-c.» to wednesday: <2011-06-29 Wed> manually added repeater: <2011-06-29 Wed +1w> «C-c .» + click on Jul 5th: <2011-07-05 Tue> -> repeater is lost :-( created another one with warning period: <2011-06-28 Tue -1d> «C-c .» + click on Jul 5th: <2011-07-05 Tue> -> warning period is lost :-( created another one with repeater and warning period: <2011-06-28 Tue +1w -1d> «C-c .» + click on Jul 5th: <2011-07-05 Tue> -> repeater and warning period is lost :-( -- Karl Voit
