From mboxrd@z Thu Jan 1 00:00:00 1970 From: cesar mena Subject: Re: org-agenda-scheduled-leaders and repeating tasks Date: Fri, 16 Oct 2015 18:24:48 -0400 Message-ID: References: <87eggueq64.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e01183eec74cfca05224043f8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37766) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZnDQg-0005tE-Mq for emacs-orgmode@gnu.org; Fri, 16 Oct 2015 18:24:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZnDQf-0004No-Ha for emacs-orgmode@gnu.org; Fri, 16 Oct 2015 18:24:50 -0400 Received: from mail-ig0-x22e.google.com ([2607:f8b0:4001:c05::22e]:33139) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZnDQf-0004Nh-89 for emacs-orgmode@gnu.org; Fri, 16 Oct 2015 18:24:49 -0400 Received: by igbkq10 with SMTP id kq10so23235328igb.0 for ; Fri, 16 Oct 2015 15:24:48 -0700 (PDT) In-Reply-To: <87eggueq64.fsf@nicolasgoaziou.fr> 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: emacs-orgmode@gnu.org --089e01183eec74cfca05224043f8 Content-Type: text/plain; charset=UTF-8 Hi Nicolas, Thanks! Your approach works for me, buy won't it trip up someone who is used to the current behaviour? Cheers -cm Hello, cesar mena 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 --089e01183eec74cfca05224043f8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Hi Nicolas,

Thanks!=C2=A0 Your approach works for me, buy won't it t= rip up someone who is used to the current behaviour?

Cheers
-cm

Hello,

cesar mena <cmena@pobox.com> w= rites:

> 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
>=C2=A0 =C2=A0 SCHEDULED: <2015-10-04 Sun .+10d>
>
> shows up in the agenda as:
>
>=C2=A0 =C2=A0 =C2=A0Sched.10x:=C2=A0 TODO check smoke alarm
>
> however, had the task been scheduled a day before (or if today was oct= 14th):
>
>=C2=A0 ** TODO check smoke alarm
>=C2=A0 =C2=A0 SCHEDULED: <2015-10-03 Sat .+10d>
>
> it would show up in the agenda as:
>
>=C2=A0 =C2=A0 =C2=A0Scheduled:=C2=A0 TODO check smoke alarm
>
> that is to say, the marker that indicates it is overdue is gone.=C2=A0= for
> some cases, like checking the smoke alarm, i don't want the "= Sched.?x"
> to reset.
>
>=C2=A0 =C2=A0 =C2=A0ie, Sched.11x:=C2=A0 TODO check smoke alarm
>
> i tracked this down to the function org-time-string-to-absolute.=C2=A0= when
> rendering the agenda it gets called with today as its DAYNR argument,<= br> > 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 mi= ss
> 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
--089e01183eec74cfca05224043f8--