From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id 4coOCjrNGl+3ZAAA0tVLHw (envelope-from ) for ; Fri, 24 Jul 2020 11:59:54 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id iPXgBTrNGl/SLwAAB5/wlQ (envelope-from ) for ; Fri, 24 Jul 2020 11:59:54 +0000 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 9B82A9403C5 for ; Fri, 24 Jul 2020 11:59:53 +0000 (UTC) Received: from localhost ([::1]:36282 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jywMh-0000Vd-E7 for larch@yhetil.org; Fri, 24 Jul 2020 07:59:51 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:46746) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jywML-0000T7-VO for emacs-orgmode@gnu.org; Fri, 24 Jul 2020 07:59:29 -0400 Received: from smtprelay07.ispgateway.de ([134.119.228.105]:6635) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jywMJ-0005Fm-H0 for emacs-orgmode@gnu.org; Fri, 24 Jul 2020 07:59:29 -0400 Received: from [46.244.219.13] (helo=condition-alpha.com) by smtprelay07.ispgateway.de with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92.3) (envelope-from ) id 1jywME-0006Z8-Nx; Fri, 24 Jul 2020 13:59:22 +0200 Message-Id: <65bb73d200b3b395e1ab36af122d8531@condition-alpha.com> From: Alexander Adolf To: Carlo Tambuatco , emacs-orgmode@gnu.org Subject: Re: Support for simultaneous running clocks? In-Reply-To: References: Date: Fri, 24 Jul 2020 13:59:22 +0200 MIME-Version: 1.0 Content-Type: text/plain X-Df-Sender: YWxleGFuZGVyLmFkb2xmQGNvbmRpdGlvbi1hbHBoYS5jb20= Received-SPF: pass client-ip=134.119.228.105; envelope-from=alexander.adolf@condition-alpha.com; helo=smtprelay07.ispgateway.de X-detected-operating-system: by eggs.gnu.org: First seen = 2020/07/24 07:59:23 X-ACL-Warn: Detected OS = Linux 3.11 and newer [fuzzy] X-Spam_score_int: -35 X-Spam_score: -3.6 X-Spam_bar: --- X-Spam_report: (-3.6 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.23 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" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Spam-Score: -0.01 X-TUID: pu7Dt9iqMkxb Hello Carlo, Org Devs, Carlo Tambuatco writes: > I don't know if anyone has suggested or is working on the ability for > org mode to keep track of multiple running clocks simultaneously. I'd > like the ability to keep track of, for example, how long something > takes to compile while I keep track of how long I am working on some > other project task at the same time. I have worked with quite a couple or work tracking tools, Org being one of them (albeit my favourite one). I learnt that running multiple clocks in parallel was an idea that didn't work out for me. In reality, I'm only ever doing one thing at a time [1]. If I want to bill that one thing multiple times, I clock it once, and just duplicate the time clocked to "the other" project(s). Or, with Org an elisp support, you can create a "magic timer", whose recorded times will be automatically copied to all "linked" projects. If I ran multiple clocks at the same time, I would - more often than not - forget to start or stop one of them, messing up my accounting. Hence, my baseline is "run a single clock only, tracking what I'm doing, and do any doubling-up-magic in the accounting". Also, to gauge build times, it might seem more promising to make the bench marking part of the build process itself ("Build took ...")? [1] https://hbr.org/2010/12/you-cant-multi-task-so-stop-tr Just my two cents anyway. Cheers, --alexander