emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Orgmode] Can't get tasks [%] and [/] to work


From: Sebastian Rose
Subject: Re: [Orgmode] Can't get tasks [%] and [/] to work
Date: Tue, 01 Sep 2009 13:30:15 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)

Michel Blanc <address@hidden> writes:
> Dear All,
>
> I probably miss something here, but I really cannot get subtasks stats
> to work (i.e. what's described in the manual at "5.5 Breaking tasks down
> into subtasks").
>
> For instance, in the snippet below :
>
> *** Cage [%]
> **** DONE Redesign motherboard
>      SCHEDULED: <2009-07-29 mer.>
>      - State "DONE"       from "TODO"       [2009-09-01 mar. 10:59]
> **** DONE Solder motherboard
>      SCHEDULED: <2009-07-30 jeu.>
>      - State "DONE"       from "TODO"       [2009-09-01 mar. 10:59]
> **** DONE Write code
>      SCHEDULED: <2009-07-31 ven.>
>      - State "DONE"       from "TODO"       [2009-09-01 mar. 10:59]
>
>
> All subentries are marked DONE, but the [%] next to cage stays empty.

> If I try to force an update with 'C-c #', I get :
>
> *** Cage [0%]
>
> which is also wrong.


`C-c #' is what doesn't work here (not sure why). But moving to some
subheading and pressing `S-LEFT S-RIGHT' will update the top headline
here.



> Another example is here :
>
> **** DONE Web interface [100%]
>     - [X] Fix lang page
>     - Implement buttons in web interface [0/1]
>       - [ ] Refresh Medias (content)
>
> 100% is wrong, since "Refresh Medias" isn't checked.
> (org-hierarchical-todo-statistics is set globally).
>
> I probably messed up things somewhere. If anyone has an idea...


How should Org-mode know, that there is a nested task? The task `Web
interface' has only children marked as DONE. This is, how it should look
like:

**** DONE Web interface [50%]
    - [X] Fix lang page
    - [ ] Implement buttons in web interface [0/1]
      - [ ] Refresh Medias (content)

There might be a variable I'm not aware of, that changes this behavior
though.


HTH,

   Sebastian




reply via email to

[Prev in Thread] Current Thread [Next in Thread]