From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jarmo Hurri Subject: Re: BUG: agenda for current days excludes reoccurring events Date: Sat, 28 Jan 2017 17:25:21 +0200 Message-ID: <8737g3cila.fsf@iki.fi> References: <87k29fbol7.fsf@iki.fi> <87o9yrs237.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34075) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cXUsl-0002yw-NR for emacs-orgmode@gnu.org; Sat, 28 Jan 2017 10:25:40 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cXUsi-0001FU-Ls for emacs-orgmode@gnu.org; Sat, 28 Jan 2017 10:25:39 -0500 Received: from [195.159.176.226] (port=44355 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cXUsi-0001F3-By for emacs-orgmode@gnu.org; Sat, 28 Jan 2017 10:25:36 -0500 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1cXUsV-00066l-Tq for emacs-orgmode@gnu.org; Sat, 28 Jan 2017 16:25:23 +0100 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: emacs-orgmode@gnu.org Greetings again. Nicolas Goaziou writes: > Jarmo Hurri writes: > >> - how the bug shows up: the reoccurring meeting will show up yesterday >> and in upcoming days, but not in the current day > > This is the consequence of `org-agenda-prefer-last-repeat' default > value. > > However, this behaviour doesn't make much sense when the entry is not > a task (i.e., it hasn't any TODO keyword). In this case, > `org-auto-repeat-maybe' doesn't apply, and the base date is never moved > forward in time. In particular the fact that you see it for all other days except today makes absolutely no sense, right? > 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. 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? Jarmo