From: Carsten Dominik <carsten.dominik@gmail.com>
To: Manish <mailtomanish.sharma@gmail.com>
Cc: Org-Mode <emacs-orgmode@gnu.org>
Subject: Re: incorrect checkbox statistics
Date: Thu, 28 Jan 2010 15:06:43 +0100 [thread overview]
Message-ID: <1F86EF50-1BB0-46BE-9522-2B324DBEAFD4@gmail.com> (raw)
In-Reply-To: <e7cdbe31001080429h35a1a8a9v49917146f217bffb@mail.gmail.com>
On Jan 8, 2010, at 1:29 PM, Manish wrote:
> Hello Carsten,
>
> The inconsistency between TODO and list statistics works now. Thanks!
>
> Statistics cookie updates still have some quirks. In "Heading 1", the
> cookie shows whatever is the value in the cookie for "item 1"
> irrespective of the number of items in the list or the cookie position
> (even COOKIE_DATA recursive is ignored, e.g. Heading 3) "Heading 4"
> works perfectly only if the leading cookie for first item does not use
> [/] or [%]. Hope these various combination are of some help.
Hi Manish,
these are useful examples, but I find it too complex to fix - this
might need a complete rewrite of the statistics code - and I don't
have the time and concentration for this. Part of the complexity is
the intermingling of TODO and checkboxes, which makes this a
complicated logic.
I keep this in my list of things to look at if I am bored, but it is
not likely to be fixed any time soon.
Patches - on the other hand - are always welcome! :-)
- Carsten
>
> --8<---------------cut here---------------start------------->8---
> * Heading 1 [1/4]
> 1. [1/4] item 1
> 1. [X] item 1.1
> 2. [ ] item 1.2
> 3. [ ] item 1.3
> 4. [ ] item 1.4
> 2. [0/2] item 2
> 1. [ ] item 2.1
> 2. [ ] item 2.2
> 3. [0/2] item 3
> 1. [ ] item 3.1
> 2. [ ] item 3.2
>
> * Heading 2 [0/4]
> 1. item 1 [0/4]
> 1. [ ] item 1.1
> 2. [ ] item 1.2
> 3. [ ] item 1.3
> 4. [ ] item 1.4
> 2. [0/2] item 2
> 1. [ ] item 2.1
> 2. [ ] item 2.2
> 3. [0/2] item 3
> 1. [ ] item 3.1
> 2. [ ] item 3.2
>
> * Heading 3 [3/4]
> :PROPERTIES:
> :COOKIE_DATA: recursive
> :END:
> 1. [3/4] item 1
> 1. [ ] item 1.1
> 2. [X] item 1.2
> 3. [X] item 1.3
> 4. [X] item 1.4
> 2. [0/2] item 2
> 1. [ ] item 2.1
> 2. [ ] item 2.2
> 3. [0/2] item 3
> 1. [ ] item 3.1
> 2. [ ] item 3.2
>
> * Heading 4 [2/9]
> :PROPERTIES:
> :COOKIE_DATA: recursive
> :END:
> 1. [-] item 1 [2/4]
> 1. [X] item 1.1
> 2. [X] item 1.2
> 3. [-] item 1.3
> 4. [ ] item 1.4
> 2. [0/2] item 2
> 1. [ ] item 2.1
> 2. [ ] item 2.2
> 3. [0/2] item 3
> 1. [ ] item 3.1
> 2. [ ] item 3.2
>
>
> --8<---------------cut here---------------end--------------->8---
>
> Regards
> --
> Manish
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
- Carsten
prev parent reply other threads:[~2010-01-28 14:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 12:29 incorrect checkbox statistics Manish
2010-01-28 14:06 ` Carsten Dominik [this message]
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=1F86EF50-1BB0-46BE-9522-2B324DBEAFD4@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mailtomanish.sharma@gmail.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).