From: Nick Dokos <nicholas.dokos@hp.com>
To: Chris Randle <chris@amlog.co.uk>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: Bug: Recurring items don't always show up in timeline
Date: Sat, 19 Mar 2011 14:46:29 -0400 [thread overview]
Message-ID: <8850.1300560389@alphaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Chris Randle <chris@amlog.co.uk> of "Sat, 19 Mar 2011 17:45:30 -0000." <4D84EBBA.2000807@amlog.co.uk>
Chris Randle <chris@amlog.co.uk> wrote:
> On 2011-03-18 21:20, Nick Dokos wrote:
> > Mark S<throaway@yahoo.com> wrote:
> >
> >> I posted this before as a question, but since it has been confirmed by
> >> others, and shows up under Linux and Windows, I'll now post the
> >> details as a bug.
> >>
> >> The Timeline view *would* be very useful for scheduling months in
> >> advance, reviewing history, or printing a year event
> >> calendar. Unfortunately, it appears that it can't really be trusted.
> >> The basic problem is that in AGENDA TIMELINE view ("C-a L") recurring
> >> items are frequently and unpredictably dropped from the view. The
> >> regular AGENDA view works fine AFAIK -- its the TIMELINE that is at
> >> issue.
> >
> > AFAICT, the culprit is org-get-all-dates: it matches date strings, translates
> > to number of days since the (imaginary) date 0001-12-31bce,
> > accumulates them in a list, sorts them, takes care of gaps - but
> > completely ignores any repeaters: iow, the "don't always show" in the
> > Subject line should more accurately say "never show".
>
> Unless I'm missing something (again!), when I try it, they *do* repeat
> *sometimes*. For example, the entry
>
> TODO [#A] Bath for dog <2011-03-10 Thu +1w>
>
> appears in agenda timeline as follows:
>
> 2011-03-10, miss 1 week, 2011-03-24, 2011-03-31, 2011-04-07, miss 7
> weeks, 2011-06-02, miss 8 weeks (agenda terminates 2011-07-31).
>
That's true. I believe that's when it coincides with another entry: it
sneaks in on the heels of the other entry. But I may very well be wrong:
I have only scratched the surface a bit.
Nick
next prev parent reply other threads:[~2011-03-19 18:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 19:02 Recurring items don't always show up in timeline Mark S
2011-03-14 20:36 ` Chris Randle
2011-03-14 22:36 ` Mark S
2011-03-15 15:39 ` Chris Randle
2011-03-14 22:55 ` Mark S
2011-03-14 23:29 ` Nick Dokos
2011-03-15 15:57 ` Chris Randle
2011-03-15 16:59 ` Nick Dokos
2011-03-15 18:17 ` Chris Randle
2011-03-15 17:34 ` Mark S
2011-03-15 18:20 ` Chris Randle
2011-03-16 17:06 ` Mark S
2011-03-18 19:58 ` Bug: " Mark S
2011-03-18 21:20 ` Nick Dokos
2011-03-19 17:45 ` Chris Randle
2011-03-19 18:46 ` Nick Dokos [this message]
2011-03-22 18:43 ` Bug: Recurring items NEVER show up in timeline unaccompanied Mark S
2011-03-22 18:59 ` Nick Dokos
2011-03-22 20:10 ` Nick Dokos
2011-03-24 7:08 ` Carsten Dominik
2011-03-24 18:40 ` Nick Dokos
2011-03-24 17:31 ` Mark S
2011-03-28 17:05 ` Carsten Dominik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8850.1300560389@alphaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=chris@amlog.co.uk \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).