From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: org-agenda-scheduled-leaders and repeating tasks
Date: Fri, 16 Oct 2015 18:25:39 +0200
Message-ID: <87eggueq64.fsf@nicolasgoaziou.fr>
References: <CAL+-AofR3rk0AQbnO5V_GJJ8p_y0NJa=KW+TVJ3-E3pGXBt26w@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:45020)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1Zn7nX-0002mA-7H
	for emacs-orgmode@gnu.org; Fri, 16 Oct 2015 12:24:04 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1Zn7nW-0005bQ-BP
	for emacs-orgmode@gnu.org; Fri, 16 Oct 2015 12:24:03 -0400
Received: from relay4-d.mail.gandi.net ([2001:4b98:c:538::196]:41540)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1Zn7nW-0005Yw-5q
	for emacs-orgmode@gnu.org; Fri, 16 Oct 2015 12:24:02 -0400
In-Reply-To: <CAL+-AofR3rk0AQbnO5V_GJJ8p_y0NJa=KW+TVJ3-E3pGXBt26w@mail.gmail.com>
	(cesar mena's message of "Tue, 13 Oct 2015 18:01:31 -0400")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=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 <cmena@pobox.com>
Cc: emacs-orgmode@gnu.org

Hello,

cesar mena <cmena@pobox.com> writes:

> i think what i am trying to say is best shown with an example.
>
> so let's say that today is oct 13th.
>
> the task
> ** TODO check smoke alarm
>    SCHEDULED: <2015-10-04 Sun .+10d>
>
> shows up in the agenda as:
>
>     Sched.10x:  TODO check smoke alarm
>
> however, had the task been scheduled a day before (or if today was oct 14th):
>
>  ** TODO check smoke alarm
>    SCHEDULED: <2015-10-03 Sat .+10d>
>
> it would show up in the agenda as:
>
>     Scheduled:  TODO check smoke alarm
>
> that is to say, the marker that indicates it is overdue is gone.  for
> some cases, like checking the smoke alarm, i don't want the "Sched.?x"
> to reset.
>
>     ie, Sched.11x:  TODO check smoke alarm
>
> 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.

Thank you.


Regards,

-- 
Nicolas Goaziou