From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Capture - stay clocked in? Date: Mon, 7 Mar 2011 13:54:52 +0100 Message-ID: <1601089B-9879-4C7C-BF74-D6010BE52C5A@gmail.com> References: <87zkp9f6m8.fsf@gnu.org> <87k4gb1u27.fsf@norang.ca> <87aah7nxuf.fsf@gnu.org> <838vwrb5as.fsf@yahoo.it> <87ipvvtedy.fsf@gnu.org> Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from [140.186.70.92] (port=52102 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PwZxl-0007Fo-74 for emacs-orgmode@gnu.org; Mon, 07 Mar 2011 07:55:02 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PwZxh-0005eJ-Kr for emacs-orgmode@gnu.org; Mon, 07 Mar 2011 07:55:00 -0500 Received: from mail-wy0-f169.google.com ([74.125.82.169]:60689) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PwZxh-0005df-Bb for emacs-orgmode@gnu.org; Mon, 07 Mar 2011 07:54:57 -0500 Received: by wyi11 with SMTP id 11so4737346wyi.0 for ; Mon, 07 Mar 2011 04:54:55 -0800 (PST) In-Reply-To: <87ipvvtedy.fsf@gnu.org> 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: Bastien Cc: Bernt Hansen , emacs-orgmode On Mar 7, 2011, at 11:26 AM, Bastien wrote: > Hi Giovanni, > > Giovanni Ridolfi writes: > >> Bastien writes: >> >>> >>> What about :clock-out t, explicitely telling org-capture-finalize to >>> clock out when? >> >> Oh, yes, please[1]! > > See my previous message -- I used :no-clock-out to stick to the default > behavior and avoid users to have to change their config. Let me know if > this is okay for you! I like this decision, because of the templates is asked to clock in, it seems natural for me that it will clock out when it is done. This only suggestion I would have is it maybe call the property :clock-keep-running. No sure though. Also, this new property, when set, does not allow :clock-resume, I have not checked if something bad would happen should a user give both by accident. Kind regards - Carsten