Re: [O] org-agenda-scheduled-leaders and repeating tasks

On Wed, Oct 28, 2015 at 9:52 AM, Nicolas Goaziou wrote: > cesar mena writes: > >> however the face is now `org-scheduled-today, as opposed to >> `org-scheduled-previously, and the agenda sorting is wrong. instead of >> bubbling to the top (since it is so

Re: [O] org-agenda-scheduled-leaders and repeating tasks

cesar mena writes: > however the face is now `org-scheduled-today, as opposed to > `org-scheduled-previously, and the agenda sorting is wrong. instead of > bubbling to the top (since it is so late) it is staying within the > "scheduled today" range. I committed another attempt

Re: [O] org-agenda-scheduled-leaders and repeating tasks

cesar mena writes: > me again :) > > the calculation is correct. > > however the face is now `org-scheduled-today, as opposed to > `org-scheduled-previously, and the agenda sorting is wrong. instead of > bubbling to the top (since it is so late) it is staying within the >

Re: [O] org-agenda-scheduled-leaders and repeating tasks

hi again nicolas, sorry. i made a mistake updating my tree. i'm quite certain i'm on master now "org-version: 8.3.2 (release_8.3.2-219-g770671)" and the repeater resets itself again. so presently i have a task that looks like this: ** TODO some task SCHEDULED: <2015-08-24 Mon ++1w> and in

Re: [O] org-agenda-scheduled-leaders and repeating tasks

cesar mena writes: > sorry. i made a mistake updating my tree. > > i'm quite certain i'm on master now "org-version: 8.3.2 > (release_8.3.2-219-g770671)" and the repeater resets itself again. > > so presently i have a task that looks like this: > > ** TODO some task >

Re: [O] org-agenda-scheduled-leaders and repeating tasks

me again :) the calculation is correct. however the face is now `org-scheduled-today, as opposed to `org-scheduled-previously, and the agenda sorting is wrong. instead of bubbling to the top (since it is so late) it is staying within the "scheduled today" range. best, -cm On Mon, Oct 26,

Re: [O] org-agenda-scheduled-leaders and repeating tasks

hi samuel, yes i suspect this is why it hasn't been reported in years. what say you nicolas? -cm On Mon, Oct 26, 2015 at 4:23 PM, Samuel Wales wrote: > fwiw, i am one who is so [disorganized?] that the old behavior is > preferred. if something is a 6m repeater, and i

Re: [O] org-agenda-scheduled-leaders and repeating tasks

fwiw, i am one who is so [disorganized?] that the old behavior is preferred. if something is a 6m repeater, and i ignore it for 6m, it's actually useful to be reminded after another repeat. perhaps more normal people would understand 1w. no matter how much i "should" mootify it or take it off

Re: [O] org-agenda-scheduled-leaders and repeating tasks

cesar mena writes: > > yes i suspect this is why it hasn't been reported in years. > > what say you nicolas? Please do not top-post :) In any case, I'm not sure Samuel complains about the current behaviour. Actually, I don't understand what is meant by "the old behaviour" in

Re: [O] org-agenda-scheduled-leaders and repeating tasks

what i am saying is that the behavior that has existed for many years for .+ timestamps, is actually useful to me. same for .+ face, sorting, and so on. just one data point.

Re: [O] org-agenda-scheduled-leaders and repeating tasks

hello guys, so far so good for me. thanks nicolas and matt. -cm On Sun, Oct 25, 2015 at 1:24 PM, Nicolas Goaziou wrote: > Nicolas Goaziou writes: > >> Matt Lundin writes: >> >>> In short, org-habit seems to want a + notation

Re: [O] org-agenda-scheduled-leaders and repeating tasks

Nicolas Goaziou writes: > Matt Lundin writes: > >> 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? > > Still looking

Re: [O] org-agenda-scheduled-leaders and repeating tasks

Matt Lundin writes: > 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? Still looking for it. Meanwhile, I reverted the opinionated change in

Re: [O] org-agenda-scheduled-leaders and repeating tasks

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

Re: [O] org-agenda-scheduled-leaders and repeating tasks

Hello, cesar mena writes: > Thanks! Your approach works for me, buy won't it trip up someone who is > used to the current behaviour? I think the previous behaviour was buggy anyway. There is no such thing as "all occurrences" for special repeaters. There may be any number of

Re: [O] org-agenda-scheduled-leaders and repeating tasks

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 > **

Re: [O] org-agenda-scheduled-leaders and repeating tasks

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

[O] org-agenda-scheduled-leaders and repeating tasks

hello everyone, 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