John Sullivan <[EMAIL PROTECTED]> writes: > Jim Ottaway <[EMAIL PROTECTED]> writes: > >> planner-appt uses planner-cyclic-diary-file to find schedule appointments. A >> line in that file such as >> >> Monday @12:00 lunch >> >> in planner-cyclic-diary-file ought to add a schedule entry on Mondays, and >> set >> up an appointment alert. It appears to work for me as intended; I have >> suggested some things for the original poster to try in a separate post. >> > > I see, I didn't know that. It seems quite odd to me to have these two > modules intertwined like that.
With respect to cyclical schedule appointments, the same file is used for both tasks and schedule items, but there are no other code entanglements since planner-cyclic ignores anything in that file that doesn't look like a task, and planner-appt does the same for schedule entries. The alternative would be to have two different files, but that would be a nuisance for the user. And the two things - cyclical tasks and cyclical schedule items - are conceptually similar anyway. Hmm. Perhaps the cyclical schedule item code really ought to be in planner-cyclic? I see I must have thought that before, since I once added a note about it in planner-appt's TODO comments. The other part of planner-appt that involves cyclical things is the forthcoming appointment display. There, the cyclical task file is examined if planner-cyclic has been required and planner-appt-forthcoming-look-at-cyclic-flag is non-nil, since then the user has indicated that they are interested in seeing forthcoming cyclical appointments. There is some further code entanglement there, since planner-appt uses the variable planner-cyclic-task-description-format in its check for duplicate task appointment items. That would be a bit trickier to disentangle. Regards, -- Jim Ottaway _______________________________________________ Planner-el-discuss mailing list [email protected] https://mail.gna.org/listinfo/planner-el-discuss
