From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Denis Bueno" Subject: Persistent clocks Date: Tue, 29 Jul 2008 21:08:14 -0400 Message-ID: <6dbd4d000807291808m68c1c548s6a55ebe2835190b8@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KO0Ar-0003xk-M4 for emacs-orgmode@gnu.org; Tue, 29 Jul 2008 21:08:17 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KO0Ap-0003wH-NX for emacs-orgmode@gnu.org; Tue, 29 Jul 2008 21:08:16 -0400 Received: from [199.232.76.173] (port=39262 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KO0Ap-0003w9-Hw for emacs-orgmode@gnu.org; Tue, 29 Jul 2008 21:08:15 -0400 Received: from an-out-0708.google.com ([209.85.132.250]:35032) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KO0Ap-0006Jy-M7 for emacs-orgmode@gnu.org; Tue, 29 Jul 2008 21:08:15 -0400 Received: by an-out-0708.google.com with SMTP id c38so27903ana.84 for ; Tue, 29 Jul 2008 18:08:14 -0700 (PDT) Content-Disposition: inline List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode Hi all, I'm a reticent poster, but long time subscriber, of this mailing list. Recently I've started using org-mode more seriously, and for various reasons which are not important, I find the current clock implementation of limited usefulness. Basically, I may restart Emacs multiple times each day, and what I'm wondering is whether persistent clocks would be easy or even useful to implement. If it's easier to change my habits than org-mode, I'm open to that. The behavior I'm thinking seems simple: - keep the clock information in drawers (as it already seems to be) - when a new org-mode file is opened and there's no clock running, scan the file for any unfinished clocks. If there is one, restart a clock from the appropriate start time. If there is more than one, signal an error. That implementation wouldn't require serialising the clock state to a different location --- just restarting the clock that was active when Emacs was killed. Does this idea make sense, and would it be useful to anyone? Or should I think about adapting my workflow to pay attention to the clock more? -- Denis