From: Nick Dokos <nicholas.dokos@hp.com>
To: throaway@yahoo.com
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: Bug: Recurring items NEVER show up in timeline unaccompanied
Date: Tue, 22 Mar 2011 14:59:18 -0400 [thread overview]
Message-ID: <3491.1300820358@alphaville.usa.hp.com> (raw)
In-Reply-To: Message from "Mark S" <throaway@yahoo.com> of "Tue, 22 Mar 2011 10:43:49 -0800." <op.vsrczbjpzpgdil@hermione2008.sd.cox.net>
Mark S <throaway@yahoo.com> wrote:
>
> You know, I think this may be the same bug I ran into 3 years ago when I
> last tried Org-mode. Is there any hope that this will be addressed? I note
> that this forum is the only location given for sending bug reports in the
> documentation.
>
> Thanks!
> Mark
>
I went looking for a bug report but the only thing that I can find
posted by you was a thread on "Getting org-agenda-sorting-strategy to
work" - nothing about the timeline. I also searched for timeline and
although there was a fair amount of activity in 2008, none of it seemed
related to this bug (I might have overlooked it of course). Can you
provide a pointer to the bug report?
Be that as it may, it will certainly be addressed when somebody provides
a patch and the maintainer applies it. *When* that will be is anybody's
guess of course (remember, everybody is a volunteer here with a day job
that might or might not leave much time for org bug fixing). But
generally speaking, once a bug bubbles to the surface, it does not stay
a bug for long.
And finally: this is the right place to post bug reports.
HTH,
Nick
PS. BTW, if you gave up on org because the timeline was not working, you
have been missing out on a bunch of good things :-) Even with a broken
timeline, org is incredibly useful. And some of us (both Chris and I e.g.,
who have been most active in the recent discussion) have never used the
timeline at all...
next prev parent reply other threads:[~2011-03-22 18:59 UTC|newest]
Thread overview: 28+ 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
2011-03-22 18:43 ` Bug: Recurring items NEVER show up in timeline unaccompanied Mark S
2011-03-22 18:59 ` Nick Dokos [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2011-03-23 18:02 Mark S
2011-03-23 18:56 ` Nick Dokos
2011-03-29 17:38 Mark S
2011-03-29 17:50 ` Carsten Dominik
2011-03-29 21:59 Mark S
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=3491.1300820358@alphaville.usa.hp.com \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=throaway@yahoo.com \
/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).