From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: BUG: agenda for current days excludes reoccurring events Date: Sat, 28 Jan 2017 19:15:49 +0100 Message-ID: <877f5frqy2.fsf@nicolasgoaziou.fr> References: <87k29fbol7.fsf@iki.fi> <87o9yrs237.fsf@nicolasgoaziou.fr> <8737g3cila.fsf@iki.fi> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58057) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cXXXW-0002ze-Jz for emacs-orgmode@gnu.org; Sat, 28 Jan 2017 13:15:55 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cXXXV-0001fp-Ox for emacs-orgmode@gnu.org; Sat, 28 Jan 2017 13:15:54 -0500 Received: from relay3-d.mail.gandi.net ([2001:4b98:c:538::195]:46444) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cXXXV-0001fW-I2 for emacs-orgmode@gnu.org; Sat, 28 Jan 2017 13:15:53 -0500 In-Reply-To: <8737g3cila.fsf@iki.fi> (Jarmo Hurri's message of "Sat, 28 Jan 2017 17:25:21 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Jarmo Hurri Cc: emacs-orgmode@gnu.org Jarmo Hurri 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,