> Ignacio Casso writes:
I can't reproduce this bug in Emacs 27.2.
>>> I'm on orgmode 9.4.6, with emacs 28.0.50.
Verified: This is fixed in the latest orgmode version (problem is gone in
9.5.2). It now clocks into different things without forgetting the rest of the
action after leaving the
Ignacio Casso writes:
>>> I can't reproduce this bug in Emacs 27.2.
>>
>> This is good news: it means I can probably proceed with bisection and
>> debugging after updating to see if the issue persists. Thanks!
>>
>> I'm on orgmode 9.4.6, with emacs 28.0.50.
>
> On second though I realize I
"Tory S. Anderson" writes:
> Ignacio Casso writes:
>
>>> Anyone else duplicating this error would be useful to know.
>>
>> I can't reproduce this bug in Emacs 27.2.
>
> This is good news: it means I can probably proceed with bisection and
> debugging after updating to see if the issue
Ignacio Casso writes:
>> Anyone else duplicating this error would be useful to know.
>
> I can't reproduce this bug in Emacs 27.2.
This is good news: it means I can probably proceed with bisection and debugging
after updating to see if the issue persists. Thanks!
I'm on orgmode 9.4.6, with
> Anyone else duplicating this error would be useful to know.
I can't reproduce this bug in Emacs 27.2.
Please send some more information like your Emacs and Org versions and
your org related configuration. See
https://orgmode.org/manual/Feedback.html for an easy way to include
this information
This is regarding the behavior of =org-log-note-clock-out=. When =nil= I can
just be clocked in to A and then when I clock in to B it stops A, starts B.
This is nice. However, when =org-log-note-clock-out= is true, I get prompted
for a note -- which is what I want -- but it stops there. So,
This is regarding the behavior of =org-log-note-clock-out=. When =nil= I can
just be clocked in to A and then when I clock in to B it stops A, starts B.
This is nice. However, when =org-log-note-clock-out= is true, I get prompted
for a note -- which is what I want -- but it stops there. So,
