From: Myles English <firstname.lastname@example.org>
To: Nicolas Goaziou <email@example.com>
Cc: Emacs-orgmode <Emacsfirstname.lastname@example.org>
Subject: Re: [bug] Effort and column view
Date: Wed, 01 Apr 2015 11:23:54 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
Nicolas Goaziou writes:
>> Myles English writes:
>>> I reported a possible bug a couple of weeks ago and since then I have
>>> notice related bugs in todays HEAD (that may have existed before).
I haven't reviewed that situation.
My original 'bug' was reported here:
>>> 1) The column view of TODO items only shows the total Effort at the
>>> top and the Effort for the last item,
>>> 2) The column view of the org-agenda (restricted to current buffer with
>>> '<', get list of todos with 't') only shows the Effort for the last item
>>> and the total Effort at the top shows the same value as for the last
>>> 3) Narrowing by tag (the original possible bug reported) shows similar
>>> behaviour as above
> I saw the bug report, but didn't find time to investigate yet. Could you
> git bisect in order to know if some commit changed that recently?
This is now an old issue but I just did a little investigation and it is
likely that it has always worked this way, so is probably more of a
feature request than a bug.
I tried versions 8.2 and 8.2.9 and they both have the same behaviour.
I may have a look (in the next few months) to see if I can make it work
the way I would like.
next prev parent reply other threads:[~2015-04-01 10:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 11:30 [bug] Effort and column view Myles English
2014-12-22 22:29 ` Myles English
2014-12-22 22:56 ` Nicolas Goaziou
2015-04-01 10:23 ` Myles English [this message]
2015-04-03 19:22 ` Nicolas Goaziou
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 \
* 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).