Jarmo Hurri <jarmo.hu...@iki.fi> writes: > In particular the fact that you see it for all other days except today > makes absolutely no sense, right?
It does make sense, but probably not when there is no TODO keyword. Also, your sentence is inaccurate: you see it _once_ in the past, not every others day. >> I think that a nil `org-agenda-prefer-last-repeat' should display : >> - only the base date when the entry has a TODO keyword; >> - every repeat between base date and today, inclusive, otherwise. >> >> It also applies to SCHEDULED and DEADLINE repeaters. >> >> Behaviour with a non-nil value needs not be changed. >> >> WDYT? > > This is slightly beyond my pay grade, but I hope a nil > 'org-agenda-prefer-last-repeat' would also display all repeats for > _future_ days. This is orthogonal to the issue. There's a dedicated variable for that: `org-agenda-show-future-repeats'. > I assume quite a few people use reoccurring entries to mark regular > meetings, short tasks etc. It is imperative that they also see how the > meeting affect the schedules of future days in their agenda. My > personal opinion is that _any entry with a timestamp_ should be > repeated as far into the future as possible, regardless of whether it > is a TODO or some other type. A timestamp indicates that this entry > very likely needs to be taken into account when scheduling future > events. Thus seeing the repetition in the agenda in the future may be > crucial. > > Does this make sense? See above. Anyway, that doesn't answer my question about what should be done for _past and present_ occurrences. If no one objects, I'll just implement the behaviour quoted above. Regards,