From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernt Hansen Subject: Re: Capture - stay clocked in? Date: Mon, 07 Mar 2011 08:51:23 -0500 Message-ID: <87bp1n11k4.fsf@norang.ca> References: <87zkp9f6m8.fsf@gnu.org> <87k4gb1u27.fsf@norang.ca> <87aah7nxuf.fsf@gnu.org> <838vwrb5as.fsf@yahoo.it> <87ipvvtedy.fsf@gnu.org> <1601089B-9879-4C7C-BF74-D6010BE52C5A@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from [140.186.70.92] (port=52338 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PwaqW-0002Go-C8 for emacs-orgmode@gnu.org; Mon, 07 Mar 2011 08:51:37 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PwaqU-0002FV-O6 for emacs-orgmode@gnu.org; Mon, 07 Mar 2011 08:51:36 -0500 Received: from mho-01-ewr.mailhop.org ([204.13.248.71]:13998) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PwaqU-0002FQ-MC for emacs-orgmode@gnu.org; Mon, 07 Mar 2011 08:51:34 -0500 In-Reply-To: <1601089B-9879-4C7C-BF74-D6010BE52C5A@gmail.com> (Carsten Dominik's message of "Mon, 7 Mar 2011 13:54:52 +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: Carsten Dominik Cc: Bastien , emacs-orgmode Carsten Dominik writes: > 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. This probably needs to be explicitly documented on what the behaviour is. I think it could easily go both ways - :no-clock-out would be true whether you resume the clock or not so we need to state what the behaviour is explicitly. If it doesn't make sense to have both :no-clock-out and :clock-resume then maybe the code could check for that and issue an error/warning when the template is selected? Maybe use :clock-keep instead of :no-clock-out (to indicate that we keep the clock running in this capture task?) and state that if you use :clock-keep then :clock-resume is ignored. I'm not sure what wording is best for this property. Regards, -- Bernt