Bastien writes:
> Bernt Hansen writes:
>
>> I see two problems with this capture:
>>
>> 1) Clock stays running in the capture task after C-c C-c
>
> I pushed a fix for this.
>
> Thanks for the minimal.emacs and the detailed report.
Hi Bastien,
Thanks. This works now.
>
>> 2) The refile.o
Hi Bernt,
Bernt Hansen writes:
> I see two problems with this capture:
>
> 1) Clock stays running in the capture task after C-c C-c
I pushed a fix for this.
Thanks for the minimal.emacs and the detailed report.
> 2) The refile.org capture buffer is narrowed hiding the newly captured
>
Bastien writes:
> Bernt Hansen writes:
>
>> For my 't' capture template with :clock-in and :clock-resume (and
>> no :clock-keep) when I start capture mode for the task when the clock is
>> not running it stays running in that task (as reported earlier) - Isn't
>> that a bug?
>
> Is it against la
Bernt Hansen writes:
> For my 't' capture template with :clock-in and :clock-resume (and
> no :clock-keep) when I start capture mode for the task when the clock is
> not running it stays running in that task (as reported earlier) - Isn't
> that a bug?
Is it against latest git? (I pushed the cha
Bastien writes:
> Carsten Dominik writes:
>
>> 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.
>
> Ah yes, thanks for bringing this up: :clock-keep has precedence
> over :clock-resume --
Carsten Dominik writes:
> 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.
Ah yes, thanks for bringing this up: :clock-keep has precedence
over :clock-resume -- when both are non-nil, :cloc
Hi Bernt,
Bernt Hansen writes:
> 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?
Done.
> Maybe use :clock-keep instead of :no-clock-out (to indicate that we keep
> the c
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 pr
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
Bastien writes:
> Bernt Hansen writes:
>
>> I think this change may have changed the default for
>> non :immediate-finish capture tasks as well.
>
> I finally introduced a new template option :no-clock-out which,
> when set to t, will prevent the clocking-out when filing an entry.
>
> This way
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 the
Hi Bernt,
Bernt Hansen writes:
> I think this change may have changed the default for
> non :immediate-finish capture tasks as well.
I finally introduced a new template option :no-clock-out which,
when set to t, will prevent the clocking-out when filing an entry.
This way the old behavior is
Bastien writes:
>
> What about :clock-out t, explicitely telling org-capture-finalize to
> clock out when?
Oh, yes, please[1]!
cheers,
Giovanni
[1] http://lists.gnu.org/archive/html/emacs-orgmode/2010-07/msg00099.html
Hi Bernt,
Bernt Hansen writes:
> I think this change may have changed the default for
> non :immediate-finish capture tasks as well.
>
> I have the following template:
>
> ("t" "todo" entry
> (file "~/git/org/refile.org")
> "* TODO %?\n%U\n%a\n" :clock-in t :clock-resume t)
>
> and if the cl
Bastien writes:
> Hi Nathan,
>
> Nathan Neff writes:
>
>> Is there an option NOT to clock out of a Todo item that's
>> created using org-capture?
>
> I assume you mean "when :immediate-finish is non-nil in a capture
> template", right?
>
> Yes, this bugged me as well.
>
> The default behavior
Hi Nathan,
Nathan Neff writes:
> Is there an option NOT to clock out of a Todo item that's
> created using org-capture?
I assume you mean "when :immediate-finish is non-nil in a capture
template", right?
Yes, this bugged me as well.
The default behavior is now (latest git) that :immediate-f
Nathan Neff writes:
> Is there an option NOT to clock out of a Todo item that's
> created using org-capture?
>
> I would like to use capture templates to define a new TODO task, and
> just stay clocked in to the new TODO.
I don't think there is an out-of-the-box way to do this today. You can
ad
Is there an option NOT to clock out of a Todo item that's
created using org-capture?
I would like to use capture templates to define a new TODO task, and
just stay clocked in to the new TODO.
Thanks,
--Nate
___
Emacs-orgmode mailing list
Please use `Re
18 matches
Mail list logo
