Re: [emacs-wiki-discuss] Diary cyclic day pages

[Jim Ottaway]

>>>>> caldwell  <address@hidden> writes:

> Hi all,
> I've been using planner since October as a TODO manager and a timeclock
> manager (very good for consulting).  I'm using a dev tar from 12/31.

> I now want to track my appointments on the day pages.  I assume that
> planner-appt is the ticket...

> I put my appointments into 
> (setq planner-cyclic-diary-file ".diary.cyclic-tasks")

> This works well when I start emacs (well means populates * Schedule with
> entries from cyclic -diary-file) but:

> Planner-goto doesn't populate * Schedule on future days.
> Planner-appt-update doesn't update * Schedule It would be nice to be
> able to get a day page from right-click in calendar

To get cyclical *schedule* items, you can set this variable to 'future:

,----[ C-h v planner-appt-schedule-cyclic-behaviour RET ]
| planner-appt-schedule-cyclic-behaviour is a variable defined in 
`planner-appt.el'.
| Its value is today
| 
| Documentation:
| Determines the behaviour of cyclical schedule insertion.
| Used after `planner-appt-schedule-cyclic-insinuate' has been called.
| 'today means only add cylical schedule entries for today
| 'future means add cyclical entries for all future day pages visited.
| 
| You can customize this variable.
| 
| [back]
`----

Unfortunately, this won't add appointments in tasks to the schedule
section at the moment: I didn't think of that when I wrote the code
for that part.  Currently, the code depends upon it being today's plan
page that is updated, so it would require quite some fiddling to deal
with future pages.

> Sooo...Is this a 'good' way of handling appointments? / How do you
> recommend seeing future appointments?

There is M-x planner-appt-forthcoming-display RET, which shows 
appointments for, in the default setting, the next seven days.

And there is also planner-appt-forthcoming-update-section-maybe, which can
be used to insert a future appointments section in today's plan page.

These are documented in the planner info file. It looks as though I
forgot to add documentation strings to the functions themselves, sorry
about that. 

I hope this helps.

Regards,

-- 
Jim Ottaway