Carsten Dominik <carsten.domi...@gmail.com> writes: > On Mar 7, 2011, at 11:26 AM, Bastien wrote: > >> Hi Giovanni, >> >> Giovanni Ridolfi <giovanni.rido...@yahoo.it> writes: >> >>> Bastien <b...@altern.org> 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
