From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Lundin Subject: Re: org-agenda-scheduled-leaders and repeating tasks Date: Wed, 21 Oct 2015 09:20:01 -0500 Message-ID: <87d1w82tim.fsf@fastmail.fm> References: <87eggueq64.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49409) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZouFM-0005sg-Gy for emacs-orgmode@gnu.org; Wed, 21 Oct 2015 10:20:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZouFJ-00020H-Al for emacs-orgmode@gnu.org; Wed, 21 Oct 2015 10:20:08 -0400 Received: from out3-smtp.messagingengine.com ([66.111.4.27]:59940) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZouFJ-0001xw-7G for emacs-orgmode@gnu.org; Wed, 21 Oct 2015 10:20:05 -0400 In-Reply-To: <87eggueq64.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Fri, 16 Oct 2015 18:25:39 +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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: cesar mena Cc: emacs-orgmode@gnu.org Nicolas Goaziou writes: > cesar mena writes: > >> i tracked this down to the function org-time-string-to-absolute. when >> rendering the agenda it gets called with today as its DAYNR argument, >> which causes "org-closest-date" to return "today" for the case of >> repeating timestamps. >> >> i can understand why it is done this way, and i find it useful. >> however for some tasks, i'd rather the counter not reset lest i miss >> something for longer than i should have (the smoke alarm case for >> example). > > I fixed the issue with a rather opinionated change. > `org-agenda-repeating-timestamp-show-all' no longer applies on ".+" and > "++" repeaters. > While I agree in principe with this change, I wonder if we could make an exception for habits. Habits (org-habit.el) customarily use a notation like this: --8<---------------cut here---------------start------------->8--- * Go for a run :PROPERTIES: :STYLE: habit :END: <2015-10-16 Fri 16:00 .+1d/2d> --8<---------------cut here---------------end--------------->8--- This will appear in the agenda with a consistency graph indicating the last n days of completion (depending on org-habit-preceding-days). Before the change in commit a427098b57c747ecc76feb0593f32922a1e12f67, these would appear in my daily agenda at their scheduled time, regardless of whether I had missed a day or two. Now, if I miss a day, the habit drops to the bottom of the agenda (it no longer appears at the scheduled time). IMO, this is undesired behavior; I want to be reminded of the habit at the same time each day regardless of whether I have done it on previous days, especially since the consistency graph gives me all the information I need about past completions. Changing the timestamp to +1d/2d will is not an option, since the timestamp only advances one day upon completion. This leads to an incoherent consistency graph. The graph color remains red, which indicates incompletion, and the habit stays on the daily agenda, even though I have just completed it. In short, org-habit seems to want a + notation for the purposes of the agenda display and a .+ notation for the purposes of resetting the timestamp. What is the best solution? Thanks, Matt