From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms13.migadu.com with LMTPS id iFhcDj98t2ZUdQEAqHPOHw:P1 (envelope-from ) for ; Sat, 10 Aug 2024 14:42:07 +0000 Received: from aspmx1.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0.migadu.com with LMTPS id iFhcDj98t2ZUdQEAqHPOHw (envelope-from ) for ; Sat, 10 Aug 2024 16:42:07 +0200 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=As4lYkAw; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=posteo.net ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1723300927; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=k5MYnhvvQb1Qz10yOfl3awcLkU7kecsM8/5ov86LH0A=; b=pVon/vcXQfzoGhA1QESbb3vlu5JGOfG/89T17ofw+/Syz20KceJyW5sdnLniRVy8JC1avd 24qib/r8fIjE+SE1tiTgDD4LfwsgNQYkSWeJoEC1UsGbL02gUX+NqSJwwff4+vouo/GgDR yID7qlQIehzjwuFoZQMWo8/yfhHUDil0W/nQTroFWuN9FwOSzFSgbtnEdn4W8RLi3rDVUW L7q79H4Q0Mh8sIvqRv2PQoKXcz/vnzYh9G6H//sOF7RAaelwYs9e+qXF0TguJShBebw5Np m8OrAZ6WNnQQAJc9c5JvKsJ5b7Tbpx6XQgC9LfALOtkZ/QqNwpH68N7jeiRHTg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=As4lYkAw; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=posteo.net ARC-Seal: i=1; s=key1; d=yhetil.org; t=1723300927; a=rsa-sha256; cv=none; b=IqO3Z1c/U/M29ItsGIQzYAwvh8Qzl8z7WZRCFXLAQYnlotkZFNTNwhMVcPyj/eIqQgwOR4 /HqJFTljrFOsl6PiiJ7zZZWiAgDHvBu7tWDrnUMtsb999M6NqSuGKNhQeX2nxp0ZnEqm9E OIVR8hDQ6aIqDvnBdiBnc9w+mNHyRxevmhprUa9SCpNclKaXcbKlUeJ1+4qjoh/F4ssCHp 6tt5eiZ0o5L5li0bEXJWCQ6PiVQvcj7KkI6DwbcEiEYPdMrrTqEhkwI9B2+PLKb70guiQB hjYSXf1FoXcgvhuU3QU3wIDh+LySUYrS775eg3+Ugcr3ruQY34K18EU6XWDrWA== Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 01AA169F62 for ; Sat, 10 Aug 2024 16:42:06 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1scnHU-0003Gh-Iw; Sat, 10 Aug 2024 10:41:20 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1scnHT-0003GT-0Q for emacs-orgmode@gnu.org; Sat, 10 Aug 2024 10:41:19 -0400 Received: from mout02.posteo.de ([185.67.36.66]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1scnHQ-0005op-IF for emacs-orgmode@gnu.org; Sat, 10 Aug 2024 10:41:18 -0400 Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 94440240103 for ; Sat, 10 Aug 2024 16:41:14 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1723300874; bh=vHeEbgeo8w5j3E9b/h9kwBU6lDcG++LGDcsMp+cMzbQ=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: From; b=As4lYkAwcx2RR4JpnmbbC6bxiAD3YpF3BNJs6+FMPuapc8zM7UHyFtjpAWcT9JJQX Sl6QwzPOd+W/eNzDctzpI0VTLkLGVQBtQp5j89eajTEEzYLgQvD/dcvST1TUQfPeGh HZuxiQWNK1FZjyZSohizY2xGbWhO5YkNztNsUu8qQT28iORePlt3vNabXDYrHGaC8y UZfPdMEp6oFeXzGqF2euIbbE2HAn093e9aupEMGrTyy9O6bI4T22Qg0Nx1T+DLBh/e 7M8vVIBEzVxULeXkamsOBDgUhnJ3wNkVpP+msNqAm62g+uoDZfrME2tRAGyRrp/GGC 4EDvlTtQkiBjg== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4Wh3PP3qB8z9rxB; Sat, 10 Aug 2024 16:41:13 +0200 (CEST) From: Ihor Radchenko To: Alexander Adolf Cc: emacs-orgmode@gnu.org, =?utf-8?Q?S=C5=82awomir?= Grochowski Subject: Re: Summation of effort estimates in columnview dblock In-Reply-To: <6ce3ea5364e48afc79f8345c67111c63@condition-alpha.com> References: <87ikwcazd9.fsf@localhost> <6ce3ea5364e48afc79f8345c67111c63@condition-alpha.com> Date: Sat, 10 Aug 2024 14:42:25 +0000 Message-ID: <8734nc30dq.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=185.67.36.66; envelope-from=yantar92@posteo.net; helo=mout02.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN X-Spam-Score: -9.67 X-Migadu-Queue-Id: 01AA169F62 X-Migadu-Scanner: mx10.migadu.com X-Migadu-Spam-Score: -9.67 X-TUID: lG2l7Zs68xyc Alexander Adolf writes: >> The manual says: >> >> SUMMARY-TYPE >> The summary type. If specified, the column values for parent nodes >> are computed from the children(1). > > The manual leaves it to the reader to figure out how the computation > happens. Nor does it mention that different column types do use > different computations, nor where to find information about the > computation applied by each column. I agree that the manual can be improved. It would be nice if someone actively using column views contributed such an improvement ;) > Btw, on the same manual page you are quoting, there is the following > footnote: > ---------------------------- Begin Quote ----------------------------- > (54) > If more than one summary type applies to the same property, the parent > values are computed according to the first of them. > ----------------------------- End Quote ------------------------------ > > At least for EFFORT, this seems ambiguous. I can have > > :format "%EFFORT %EFFORT{:}" > > and both columns are present, and computed differently, whereas the > footnote can easily be read as hinting to the opposite. In fact, the > footnote is correct for all time format properties _except_ EFFORT. Not sure here. %EFFORT should not count. I tried the following: #+COLUMNS: %EFFORT{mean} %EFFORT{+} * Foo :PROPERTIES: :EFFORT: 15.0 <-- gets updated :END: ** Bar :PROPERTIES: :EFFORT: 20 :END: ** Baz :PROPERTIES: :EFFORT: 10 :END: >> In other words, Org mode computes the value of the property for your >> Task 1, from Task 1.1, and Task 1.2. Whatever is inside Task 1 does not >> matter. > > This is true for EFFORT, and all other time format (real) property > columns, but not for CLOCKSUM columns. Yes, same for other special properties - they cannot be set in properties drawer and are handled differently. > What has added to my perceived need of help, prompting me to start this > thread, is that the manual is extremely tight lips in this area. > > It would thus seem helpful to readers (hope not just myself), if the > "column attributes" section (the one with the SUMMARY-TYPE definition > you quoted) could be extended: > > - With a new paragraph or two at the very end explaining how the normal > ("%Property"), and colon summations ("%Property{:}") of time format > properties are done, and what gets overwritten when. The section now > ends with an example containing such a column, so the explanation > would fit nicely there, IMHO. +1 > - Right after that, with another new paragraph explaining how the > summation for CLOCKSUM and CLOCKSUM_T is done in contrast, and > mentioning that nothing is ever overwritten for these. +1 > - The section should also mention that the footnote # 54, which I quoted > above, does not apply to the (special-ish) EFFORT property. It looks like it does apply, AFAIU. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at