From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms1.migadu.com with LMTPS id eCflL5+UGmaA1AAAe85BDQ:P1 (envelope-from ) for ; Sat, 13 Apr 2024 16:20:16 +0200 Received: from aspmx1.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2.migadu.com with LMTPS id eCflL5+UGmaA1AAAe85BDQ (envelope-from ) for ; Sat, 13 Apr 2024 16:20:15 +0200 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=cbM1EIsh; dmarc=pass (policy=none) header.from=posteo.net; 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" ARC-Seal: i=1; s=key1; d=yhetil.org; t=1713018015; a=rsa-sha256; cv=none; b=Rd+MyW2HZtoFF59LKJGiC+in92/nY5R9oF43umghIX4EkGkIHwaxKT0fDCuAP8MgA/oACn OOjP4tfjpyO8xFtmyPWUXTgFxnR7DpB3pKBabwAm7dTpiZwtaULv46dJy3kLh1dtHp53oa k9u0u/GpdryWk/zHLm8RX0OZcAxZbPlXulBsm9AaUqVld9uCJFtqcm/sXw+yAGkP3fE2k6 xjXN+hIlbEo71nQ1fKyxBc8NnF0CnFJj0vRBDjDgH2jR+t9ELreV/x30G1Kpb5vktZpt8T HbPaCJzzjrHW8L+/wKQiIMJVacUQVdYzV4E1tTzK8usc6QGRYrTGHO18iYPcdA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=cbM1EIsh; dmarc=pass (policy=none) header.from=posteo.net; 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" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1713018015; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=LRAF2L1+xab67GfanqnPOxzqKdr8r+Gzm746SUswmq8=; b=W+QMPkfI53UKTkjOP9BKAjcK6xp67Bm1ek4f6UQTXpL4JbMjai1tqY4j7q4jgGo0Go16R9 UnGwSlm4f6p1a7e5gRRN+PA9wWXHcdjUKKxxGIKd2wPaSe7NoZIbkxlTnpj4UJmy5s+r/X bBX3On0Dia9uW6jYVkahOdiLRzJh7MoqKXNieF+KyPcBlhnVLmFYztbpIq363oA2urof46 rfDlajM7LwrRTOEgjOa5wHk/OM5IA9HQjPU2MFBl3oCMjzN0HLMHqmYFkLbkweZwewx2lB 3rzUCih/fpRw5xum8+QNLhpyWyWqwdwBKKiF+Gi6xM1Omnsz/NecrTZErXMOJw== 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 84A806FE6F for ; Sat, 13 Apr 2024 16:20:15 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rveE7-0004Io-8f; Sat, 13 Apr 2024 10:19:31 -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 1rveE5-0004IX-HX for emacs-orgmode@gnu.org; Sat, 13 Apr 2024 10:19:29 -0400 Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rveE3-0000l1-K1 for emacs-orgmode@gnu.org; Sat, 13 Apr 2024 10:19:29 -0400 Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 1AEC0240028 for ; Sat, 13 Apr 2024 16:19:24 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1713017965; bh=r6FLvI79riFdZZ02d+con+3stf5UFs+QrBTB1F8nA2g=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: Content-Transfer-Encoding:From; b=cbM1EIshEPLHIb57OJ6o3i7ySJYl5D0PJydhVZfb3VRDupn4hDW0I0fK8B+m7K4oT qymCaTRjKx+wNoAyeVSwR60YoAi4PYTFierYxNka+0isNPOG50UoLxR+/uzvt/CS9U AJV9Om2W1PY2JB0wq607He5erX3GNY7q+uwft1x6uBejl7q3cyU7oMMkomBLl6i+yd E+syhz6sfX+urRdRHt5b9OI52i4KUPRBnMNL6B5BxfqIX9/a6JZDoP360s88dIV8CT uyTk8aKvQN//ENwTBFRMiGF8CiiY6csT6HG4KL6z4N2dBByziPmXqkRuLo35F4fdWa Bh0D99uRs4wvg== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4VGwY814gxz6twv; Sat, 13 Apr 2024 16:19:23 +0200 (CEST) From: Ihor Radchenko To: Alexander Adolf Cc: emacs-orgmode@gnu.org Subject: Re: columnview dynamic block - different time summing behaviour for EFFORT and CLOCKSUM In-Reply-To: <00aa9bf72dc93f6554bdd236fdfba192@condition-alpha.com> References: <486d2b818b62c71b3f307305c06c4318@condition-alpha.com> <871q7cypxl.fsf@localhost> <00aa9bf72dc93f6554bdd236fdfba192@condition-alpha.com> Date: Sat, 13 Apr 2024 14:19:54 +0000 Message-ID: <87y19hbb05.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=185.67.36.65; envelope-from=yantar92@posteo.net; helo=mout01.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, 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-Flow: FLOW_IN X-Migadu-Country: US X-Spam-Score: -6.59 X-Migadu-Queue-Id: 84A806FE6F X-Migadu-Spam-Score: -6.59 X-Migadu-Scanner: mx10.migadu.com X-TUID: iI7G7XViIXQi Alexander Adolf writes: >> In fact, CLOCKSUM property does not support custom summaries. > > ??? AFAIU, you cannot do %CLOCKSUM{max}. >>> Is there any way to change the summation behaviour for either or both >>> column types? >> >> It is currently hard-coded. (Although, it is not too hard add some kind >> of switch). >> [...] > > I think that instead of a switch, I would prefer the columnview dblock > to get a :formatter added. Knowing how the values have been computed in > the dblock's write function, I can re-calculate whatever data I need in > the formatter. > > I am already using this approach successfully with the clocktable dblock > to generate invoices for me. > > Compared to a new switch, it would seem to me that adding a :formatter > to the columnview dblock has several advantages: > > - it would likely be a smaller code change; > > - instead of implementing a single, new behaviour (activated by switch) > it would give users the flexibility to implement any new behaviour > they might want (user-supplied :formatter function). > > > Thus, from my point of view, having a :formatter for the columnview > dblock would be quite fabulous. =F0=9F=A6=84=F0=9F=98=9C This will not prevent the property values from being changed by column view. In any case, making column views more flexible is welcome. --=20 Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at