Hi Dennis, thanks for the patch.
I am not sure yet if you are using the right condition though. It
seems to me that extending the late-warning-period makes sens only for
repeating *tasks*, where the base date keeps changing each time you
mark this entry as DONE. So maybe the condition
I'm using the agenda to keep my important tasks 'in my face' so they get
dealt with. This is normally the only place my repeating tasks show up.
If I miss a repeating task for a few days for some reason the worst
thing (for me) that can happen is it falls off the agenda for some time
without
Salutations!
Hi Dennis, thanks for the patch.
I am not sure yet if you are using the right condition though. It seems to
me that extending the late-warning-period makes sens only for repeating
*tasks*, where the base date keeps changing each time you mark this entry
as DONE. So maybe
I prefer the same way. I wish to have full confidence that anything
scheduled but not done will show up in my agenda.
Thanks.
Wanrong
Bernt Hansen wrote:
I'm using the agenda to keep my important tasks 'in my face' so they get
dealt with. This is normally the only place my repeating tasks
Salutations!
Please note that I'm sending this from gnus talking to gmane, and this
is the first time that I've tried posting anything to gmane (or using
gnus), so apologies if the electrons don't exactly align.
Wanrong Lin [EMAIL PROTECTED] writes:
repeat TODO items has changed. Seems it did
Please post your code, you can always do this, the copyright question
only star when we decide to use it. And even then, 4 lines is very
little.
- Carsten
On Jan 18, 2008, at 10:24 PM, Dennis J Lin wrote:
Salutations!
Please note that I'm sending this from gnus talking to gmane, and this
Salutations!
Please post your code, you can always do this, the copyright question
only star when we decide to use it. And even then, 4 lines is very little.
Sure, please see it below :-)
Dennis Lin
Basically, in org-agenda-get-scheduled, we call
org-time-string-to-absolute passing in d1
