From mboxrd@z Thu Jan 1 00:00:00 1970 From: Warren Lynn Subject: Re: Bug: Repeated tasks not shown from org-timeline [9.0 (9.0-dist @ c:/wlin/.emacs-lisp/org/lisp/)] Date: Mon, 7 Nov 2016 13:18:25 -0500 Message-ID: References: <87d1ibay4n.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=94eb2c191e26cbab610540ba0cda Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33508) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c3oV2-0004md-9s for emacs-orgmode@gnu.org; Mon, 07 Nov 2016 13:18:29 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c3oV1-0000y6-5t for emacs-orgmode@gnu.org; Mon, 07 Nov 2016 13:18:28 -0500 Received: from mail-yb0-x234.google.com ([2607:f8b0:4002:c09::234]:35971) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1c3oV1-0000xr-1V for emacs-orgmode@gnu.org; Mon, 07 Nov 2016 13:18:27 -0500 Received: by mail-yb0-x234.google.com with SMTP id v78so58714682ybe.3 for ; Mon, 07 Nov 2016 10:18:26 -0800 (PST) In-Reply-To: <87d1ibay4n.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" To: Warren Lynn , emacs-orgmode@gnu.org --94eb2c191e26cbab610540ba0cda Content-Type: text/plain; charset=UTF-8 Thanks. I have been using org mode for probably over 10 years, but did not keep checking the messages. The feature is very useful to me. Do you have any suggestion how to replicate this with an agenda view (with skipped empty days, especially)? Thanks. On Fri, Nov 4, 2016 at 2:38 PM, Nicolas Goaziou wrote: > Hello, > > Warren Lynn writes: > > > With a simple org file of just one entry as below: > > > > * TODO A weekly task > > SCHEDULED: <2016-11-04 Fri +1w> > > > > If I run org-timeline, I expect to see this task show up on every > > Friday. But only one line is in the timeline, for "2016-11-04" > > only. This behavior will make user have doubts when checking a date in > the > > timeline. > > > > BTW: if we change the above file into the following: > > > > * TODO A weekly task > > SCHEDULED: <2016-11-04 Fri +1w> > > * TODO Some other task in next week. > > SCHEDULED: <2016-11-11 Fri> > > > > Then orgline WILL show the repeat task for "2016-11-11". > > Org Timeline is pretty much deprecated. Carsten pointed out its > limitations years ago already (I cannot find the references on the ML, > tho). > > I suggest to stay away from this feature, which ought to be removed at > some point. You can probably obtain the same feature with an agenda view > restricted to buffer. > > Regards, > > -- > Nicolas Goaziou > --94eb2c191e26cbab610540ba0cda Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thanks. I have been using org mode for probably over = 10 years, but did not keep checking the messages.

The feature= is very useful to me. Do you have any suggestion how to replicate this wit= h an agenda view (with skipped empty days, especially)? Thanks.

On Fri, Nov 4, 2016= at 2:38 PM, Nicolas Goaziou <mail@nicolasgoaziou.fr> w= rote:
Hello,

Warren Lynn <wrn.lynn@gmail.com> writes:

> With a simple org file of just one entry as below:
>
> * TODO A weekly task
>=C2=A0 =C2=A0SCHEDULED: <2016-11-04 Fri +1w>
>
> If I run org-timeline, I expect to see this task show up on every
> Friday. But only one line is in the timeline, for "2016-11-04&quo= t;
> only. This behavior will make user have doubts when checking a date in= the
> timeline.
>
> BTW: if we change the above file into the following:
>
> * TODO A weekly task
>=C2=A0 =C2=A0SCHEDULED: <2016-11-04 Fri +1w>
> * TODO Some other task in next week.
>=C2=A0 =C2=A0SCHEDULED: <2016-11-11 Fri>
>
> Then orgline WILL show the repeat task for "2016-11-11".

Org Timeline is pretty much deprecated. Carsten pointed out its
limitations years ago already (I cannot find the references on the ML,
tho).

I suggest to stay away from this feature, which ought to be removed at
some point. You can probably obtain the same feature with an agenda view restricted to buffer.

Regards,

--
Nicolas Goaziou

--94eb2c191e26cbab610540ba0cda--