Re: [O] Old entry remains in appt when the original one in org file is changed

Hi Bernt, My recipe clears the list each time the agenda is generated.  I only use appt for org-mode appointments so clearing the list works great for me. Sorry I missed (setq appt-time-msg-list nil) in your setup code. This is exactly what happens when you pass non-nil for REFRESH argument

Re: [O] Old entry remains in appt when the original one in org file is changed

Takafumi Arakaki aka@gmail.com writes: Hi Bernt, Thanks for your setup recipe. However, I noticed I failed to explain what I meant; the old entry remains in appt-time-msg-list even if you call org-agenda-to-appt. My recipe clears the list each time the agenda is generated. I only use

Re: [O] Old entry remains in appt when the original one in org file is changed

Hi Bernt, Thanks for your setup recipe. However, I noticed I failed to explain what I meant; the old entry remains in appt-time-msg-list even if you call org-agenda-to-appt. So, the procedure to reproduce my problem is the following: 1. Add the following in the agenda file * TODO test

Re: [O] Old entry remains in appt when the original one in org file is changed

Takafumi Arakaki aka@gmail.com writes: I am using org-agenda-to-appt and I noticed a bug. 1. Add the following in the agenda file * TODO test SCHEDULED: 2012-01-14 Sat 12:00 2. Call org-agenda-to-appt 3. Change the SCHEDULED time-stamp in the entry like this * TODO test

[O] Old entry remains in appt when the original one in org file is changed

I am using org-agenda-to-appt and I noticed a bug. 1. Add the following in the agenda file * TODO test SCHEDULED: 2012-01-14 Sat 12:00 2. Call org-agenda-to-appt 3. Change the SCHEDULED time-stamp in the entry like this * TODO test SCHEDULED: 2012-01-14 Sat 12:00 4. appt-time-msg-list