emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Derek Upham <sand@blarg.net>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-agenda-show-log, org-timeline bugs
Date: Sat, 16 Feb 2013 16:54:32 -0800	[thread overview]
Message-ID: <878v6n220n.fsf@priss.frightenedpiglet.com> (raw)
In-Reply-To: <87pq04wkwo.fsf@bzg.ath.cx>

Bastien writes:
> Sorry, no special effort is made to fix bugs in org-timeline because
> its future is uncertain: there is significant overlap between this
> feature from the early days of Org, and the general agenda views
> mechanism.
> We'll make a decision about org-timeline before releasing Org 8.0: 
> if it stays, let's fix it.  If it goes, let's forget it!

I found these bugs when I was using org-timeline to get an overview of
work done during the past several months.  The rest of the agenda code
is forward-facing, so looking at historical data is one area where there
is no overlap.  Whether or not it needs to be part of the agenda
framework is another matter.


Derek Upham

  reply	other threads:[~2013-02-17  0:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04  8:33 org-agenda-show-log, org-timeline bugs Derek Upham
2013-02-07 15:00 ` Derek Upham
2013-02-13 11:54   ` Bastien
2013-02-17  0:54     ` Derek Upham [this message]
2013-04-13  9:47 ` Bastien

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:

  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=878v6n220n.fsf@priss.frightenedpiglet.com \
    --to=sand@blarg.net \
    --cc=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \


* 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


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).