emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Myles English <mylesenglish@gmail.com>
To: Emacs-orgmode <Emacs-orgmode@gnu.org>
Subject: Re: CLOCKSUM counts appointments excluded by tag
Date: Tue, 9 Dec 2014 22:48:26 +0000	[thread overview]
Message-ID: <CAO=Do-whdm-hqzukhM6fZyueHf=v9rKeJp2ALF-um=oBLg1n3w@mail.gmail.com> (raw)
In-Reply-To: <CAO=Do-zHxSmuBwqkdG3C89zTKj9baK888qqXKayGuz_fCK=7fg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4049 bytes --]

On 9 December 2014 at 21:35, Myles English <mylesenglish@gmail.com> wrote:

> I made a mistake in my first mail: the totals are for the Effort property
> not CLOCKSUM.
>
> Can no one confirm this?  Is there something else wrong with my post?  The
> situation is the same after pulling from master today.
>
>
> On 4 December 2014 at 22:58, Myles English <mylesenglish@gmail.com> wrote:
>
>> Hello,
>>
>> I am using git master from yesterday (commit 6d2a661f) and have found
>> that when the agenda is narrowed by tag (i.e. all appointments marked
>> with a certain tag are excluded), the clocksum still shows the
>> un-narrowed total.  Is this the correct behaviour, or a bug?
>>
>> Selected variables:
>>
>> org-agenda-columns-add-appointments-to-effort-sum is t
>> org-columns-default-format:
>> "%80ITEM(Task) %10Effort(Effort){:} %10Duration(Duration){:} %10CLOCKSUM"
>>
>> org-global-properties:
>> (("Effort_ALL" . "0:00 0:10 0:30 1:00 2:00 3:00 4:00 5:00 6:00 7:00 8:00
>> 16:00 24:00 32:00"))
>>
>> Test org file:
>>
>>
>> ;;,------------------------------------------------------------------------------
>> ;;| * Nail org mode bug
>> ;;|   SCHEDULED: <2014-12-04 Thu 9:00-10:00>
>> ;;|
>> ;;| * Earn money
>>  :spouse:
>> ;;|   SCHEDULED: <2014-12-04 Thu 09:00-20:00>
>> ;;|
>> ;;| * Drink tea
>> ;;|   SCHEDULED: <2014-12-04 Thu 10:00-16:00>
>>
>> ;;`------------------------------------------------------------------------------
>>
>>
>> C-c a < a       ;; get the agenda for the current test file
>> C-c C-x C-c     ;; turn on column view
>>
>> ;;,------------------------------------------------------------------
>> ;;| Thursday    4 December 2014                             | 18:00 |
>> ;;|                8:00...... ----------------
>> ;;| * Nail org mode bug                                     | 1:00  |
>> ;;| * Earn money                                            | 11:00 |
>> ;;| * Drink tea                                             | 6:00  |
>> ;;`------------------------------------------------------------------
>>
>>
>> / - TAB 'spouse' ;; narrow by excluding the item tagged 'spouse'
>>
>> See how the 18:00 has counted the 11:00 that should have been excluded:
>>
>> ;;,------------------------------------------------------------------
>> ;;| Thursday    4 December 2014                             | 18:00 |
>> ;;|                8:00...... ----------------
>> ;;| * Nail org mode bug                                     | 1:00  |
>> ;;| * Drink tea                                             | 6:00  |
>> ;;`------------------------------------------------------------------
>>
>> I would have expected something this:
>>
>> ;;,-----------------------------------------------------------------
>> ;;| Thursday    4 December 2014                             | 7:00 |
>> ;;|                8:00...... ----------------
>> ;;| * Nail org mode bug                                     | 1:00 |
>> ;;| * Drink tea                                             | 6:00 |
>> ;;`-----------------------------------------------------------------
>>
>> and am therefore disappointed.
>>
>> I haven't investigated if this happens for simple clocked time as well
>> as appointments yet.
>>
>
Yes, I can see similar behaviour for clocked tasks.  That is to say, with
this file contents:

#+COLUMNS: %40ITEM(Task) %17Effort(Estimated Effort){:} %CLOCKSUM
* TODO Earn money
  :PROPERTIES:
  :Effort:   0:10
  :END:

* TODO Drink tea                              :a:
  :PROPERTIES:
  :Effort:   0:30
  :END:

#start emacs
$ emacs -Q

M-x org-agenda
<                 ;; narrow to current buffer
t                   ;; see all TODOs
C-c C-x C-c  ;; see column view
/  - TAB a     ;; exclude the item tagged :a:

And the result looks something like this:

Task                                                       | Estimated
Effort
____________________________________________________
Global list of TODO items of type: ALL
Available with `N r': (0)[ALL] (1)TODO   | 0:40
  TODO Earn money                              | 0:10


Myles

[-- Attachment #2: Type: text/html, Size: 5572 bytes --]

  reply	other threads:[~2014-12-09 22:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-04 22:58 CLOCKSUM counts appointments excluded by tag Myles English
2014-12-09 21:35 ` Myles English
2014-12-09 22:48   ` Myles English [this message]
2015-01-16  9:00     ` Nicolas Goaziou

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='CAO=Do-whdm-hqzukhM6fZyueHf=v9rKeJp2ALF-um=oBLg1n3w@mail.gmail.com' \
    --to=mylesenglish@gmail.com \
    --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).