Hi, Bastien Thanks for the patch and I am sorry for this late reply (especially because I pushed maintainers to review my patch before...).
Anyway, I tried the head of master (580add2f4148fea949a4db5550577911ee6d756e) and it works fine for me. But I couldn't reproduce this behavior: > Note that timestamps need to be well formatted. If there is > a +3d repeat cookie and the original timestamp doesn have any > indication for the hour, it will produce an error. (BTW, you mean +3h, right?) There is no change in the SCHEDULE time stamp, but I've got state change log and LAST_REPEAT in PROPERTIES. Note that I have `(setq org-log-into-drawer t)' in my configuration. Resulting tree was something like this (I changed the state to DONE three times): * TODO Test SCHEDULED: <2012-04-26 Thu +3h> :LOGBOOK: - State "DONE" from "TODO" [2012-04-26 Thu 16:16] - State "DONE" from "TODO" [2012-04-26 Thu 16:16] - State "DONE" from "TODO" [2012-04-26 Thu 16:16] :END: :PROPERTIES: :LAST_REPEAT: [2012-04-26 Thu 16:16] :END: Regarding not using constant for "dwmy". > I didn't replace "dwmy" by a constant though, this is not expected > to change anymore. I think somebody may want to have minute cookie. And in that case, repeating the same task is tiresome. I didn't put minute in my patch simply because I didn't know what letter I should use. I guess no one wants second or century though. So maybe we should decide what letter to use for minute and change "dwmy" again, if you don't like the constant solution? -- Takafumi