On 2023-02-17, at 19:14, Ihor Radchenko wrote:
> Marcin Borkowski writes:
>
>>> Another thing you can try is setting org-element--cache-self-verify to
>>> nil.
>>
>> That did help indeed. Should I make it nil in my init.el?
>
> You can, as long as you do not see warnings from Org about
> org-
Marcin Borkowski writes:
>> Another thing you can try is setting org-element--cache-self-verify to
>> nil.
>
> That did help indeed. Should I make it nil in my init.el?
You can, as long as you do not see warnings from Org about
org-element-cache. This variable is enabling extra consistency chec
On 2023-02-17, at 14:32, Ihor Radchenko wrote:
> Marcin Borkowski writes:
>
>>> Do you have org-element-use-cache set to nil?
>>
>> No, should I?
>
> You should not. But, when it is nil (not default), things will be slow
> in your scenario.
>
> Another thing you can try is setting org-element-
Marcin Borkowski writes:
>> Do you have org-element-use-cache set to nil?
>
> No, should I?
You should not. But, when it is nil (not default), things will be slow
in your scenario.
Another thing you can try is setting org-element--cache-self-verify to
nil.
If it does not help either, please do
On 2023-02-17, at 13:02, Ihor Radchenko wrote:
> Marcin Borkowski writes:
>
>> I have just updated my Org (from the main branch, Org mode version
>> 9.6.1, release_9.6.1-253-g74eb0f), and I noticed an issue with clocking.
>> I have an "ongoing" task which already accumulated 7000+ clock entrie
Marcin Borkowski writes:
> I have just updated my Org (from the main branch, Org mode version
> 9.6.1, release_9.6.1-253-g74eb0f), and I noticed an issue with clocking.
> I have an "ongoing" task which already accumulated 7000+ clock entries,
> and clocking in takes close to 90 seconds. It was i
On 2023-02-17, at 07:51, Marcin Borkowski wrote:
> Hi all,
>
> I have just updated my Org (from the main branch, Org mode version
> 9.6.1, release_9.6.1-253-g74eb0f), and I noticed an issue with clocking.
> I have an "ongoing" task which already accumulated 7000+ clock entries,
> and clocking i
Hi all,
I have just updated my Org (from the main branch, Org mode version
9.6.1, release_9.6.1-253-g74eb0f), and I noticed an issue with clocking.
I have an "ongoing" task which already accumulated 7000+ clock entries,
and clocking in takes close to 90 seconds. It was instantaneous before
(versi
