From: Eric S Fraga <email@example.com>
To: Bastien <firstname.lastname@example.org>
Cc: Michael Brand <email@example.com>,
Org Mode <firstname.lastname@example.org>
Subject: Re: Statistic cookies for headings and list items
Date: Mon, 01 Jun 2020 14:51:32 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (Bastien's message of "Mon, 01 Jun 2020 15:29:23 +0200")
On Monday, 1 Jun 2020 at 15:29, Bastien wrote:
> I believe we cannot fix this without a discussion on the design first.
Good to be able to discuss this. I won't repeat the options but will
give my own views as I do use statistic cookies quite a bit.
I would accept either 1 and/or 2 with or without 3. However, I do not
like option 4 at all as this would simply lead to confusion. There is
no obvious way to understand the implication of the placement of the
cookie by looking at it.
However, what I would really like to have is the option to include both
lists and subheadings (recursively) in the statistics, i.e. count all
below a given point whether the entries appear as a direct contents list
or lists within subheadings. I usually end up with lists of lists,
which is fine (and very lispy... ;-)), but when these get long, they are
harder to navigate and hide/open than headings are.
(note: it could be that what I want is ready possible as I'm often
caught out on this list for missing existing functionality. If so, I
: Eric S Fraga via Emacs 28.0.50, Org release_9.3.6-640-g9bc0cc
next prev parent reply other threads:[~2020-06-01 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 19:31 Statistic cookies for headings and list items Michael Brand
2020-06-01 13:29 ` Bastien
2020-06-01 13:51 ` Eric S Fraga [this message]
2020-06-13 16:15 ` Nicolas Goaziou
2021-05-15 20:28 ` Bastien
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).