Ihor Radchenko <[email protected]> writes:
> If we want to extend the API this way, we should discuss it in more
> details. What exactly does RECURSIVE do? Isn't the current default
> (implied RECURSIVE=nil) actually doing the recursion by default?
You are completely right. The word "recursive" felt off to me as well,
as column view already computes recursively bottom-up. I only stuck
with it because of the existing COOKIE_DATA property ("recursive").
I think it is a good opportunity to clarify the terminology across Org:
1. Support "subtree" in COOKIE_DATA (retaining "recursive" for backward
compatibility). This aligns with `org-*-children-only-statistics',
clearly contrasting children with the entire subtree.
2. In column view, introduce subtree operators named "Xs", "Xs/", and
"Xs%" ("s" for subtree).
3. I dropped the idea of extending the custom summary type API for now,
keeping this change simple and focused.
What do you think about this direction?
Best,
--
Slawomir Grochowski