From: Bernt Hansen <bernt@norang.ca>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Bastien <bzg@altern.org>, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Capture - stay clocked in?
Date: Mon, 07 Mar 2011 08:51:23 -0500 [thread overview]
Message-ID: <87bp1n11k4.fsf@norang.ca> (raw)
In-Reply-To: <1601089B-9879-4C7C-BF74-D6010BE52C5A@gmail.com> (Carsten Dominik's message of "Mon, 7 Mar 2011 13:54:52 +0100")
Carsten Dominik <carsten.dominik@gmail.com> writes:
> On Mar 7, 2011, at 11:26 AM, Bastien wrote:
>
>> Hi Giovanni,
>>
>> Giovanni Ridolfi <giovanni.ridolfi@yahoo.it> writes:
>>
>>> Bastien <bzg@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
next prev parent reply other threads:[~2011-03-07 13:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 19:30 Capture - stay clocked in? Nathan Neff
2011-02-28 22:40 ` Bernt Hansen
2011-03-06 0:13 ` Bastien
2011-03-07 3:35 ` Bernt Hansen
2011-03-07 8:23 ` Bastien
2011-03-07 10:20 ` Giovanni Ridolfi
2011-03-07 10:26 ` Bastien
2011-03-07 12:54 ` Carsten Dominik
2011-03-07 13:51 ` Bernt Hansen [this message]
2011-03-07 14:44 ` Bastien
2011-03-07 14:45 ` Bastien
2011-03-07 15:20 ` Bernt Hansen
2011-03-07 15:28 ` Bastien
2011-03-07 15:55 ` Bernt Hansen
2011-03-07 16:27 ` Bastien
2011-03-07 18:13 ` Bernt Hansen
2011-03-07 10:17 ` Bastien
2011-03-07 12:34 ` Bernt Hansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bp1n11k4.fsf@norang.ca \
--to=bernt@norang.ca \
--cc=bzg@altern.org \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).