From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard Riley Subject: Re: clock and WAIT Date: Fri, 15 Jan 2010 18:10:06 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NVpkw-0001us-DD for emacs-orgmode@gnu.org; Fri, 15 Jan 2010 12:14:42 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NVpkr-0001nh-Fc for emacs-orgmode@gnu.org; Fri, 15 Jan 2010 12:14:42 -0500 Received: from [199.232.76.173] (port=50158 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NVpkr-0001nV-Bn for emacs-orgmode@gnu.org; Fri, 15 Jan 2010 12:14:37 -0500 Received: from mx20.gnu.org ([199.232.41.8]:31063) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NVpkr-0000Y0-3U for emacs-orgmode@gnu.org; Fri, 15 Jan 2010 12:14:37 -0500 Received: from lo.gmane.org ([80.91.229.12]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NVpkp-00070R-KH for emacs-orgmode@gnu.org; Fri, 15 Jan 2010 12:14:35 -0500 Received: from list by lo.gmane.org with local (Exim 4.50) id 1NVpi5-00064e-Vw for emacs-orgmode@gnu.org; Fri, 15 Jan 2010 18:11:46 +0100 Received: from 85.183.18.158 ([85.183.18.158]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 15 Jan 2010 18:11:45 +0100 Received: from rileyrgdev by 85.183.18.158 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 15 Jan 2010 18:11:45 +0100 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@gnu.org Manish writes: > On Fri, Jan 15, 2010 at 4:52 PM, Richard Riley wrote: >> >> When I put a task into certain states it would be nice to stop the clock >> automatically. It is done for DONE at the moment. >> >> Would it make sense to make >> >> org-clock-out-when-done >> >> a list of state names rather than (or in addition to) a bool? >> >> That way I could make it DONE, WAIT so when I cycle the state to WAIT (eg for >> an email confirming something works) the clock is stopped automatically? >> >> Or is there another mechanism for this? Or is the mantra more to keep >> stop/start manual until the obvious state for "DONE"? >> > > Not for a list of states but it can be done for at least one state. > See variable org-clock-out-switch-to-state. > > HTH Thats a different issue. That determines which state the task is automatically switched to when you actually remember to clock out. I'm not sure I would find that useful since there are multiple states I might be in with and without the clock running and I wouldnt want stopping the clock to reset the state. -- Google Talk : rileyrgdev@googlemail.com http://www.google.com/talk