On 20/05/2023 22:01, Ihor Radchenko wrote:
> You can try to bisect your config to identify which part is triggering
> the problem. See
> https://list.orgmode.org/orgmode/87ee2nlslt.fsf@localhost/ and
> https://github.com/Malabarba/elisp-bug-hunter
I have been able to create a minimal set of init.e
On 20/05/2023 22:01, Ihor Radchenko wrote:
> You can try to bisect your config to identify which part is triggering
> the problem. See
> https://list.orgmode.org/orgmode/87ee2nlslt.fsf@localhost/ and
> https://github.com/Malabarba/elisp-bug-hunter
I have "bisected" init.el to no avail, the problem
On 20/05/2023 18:04, Ihor Radchenko wrote:
I am unable to reproduce.
Could you please try to detail all the steps more precisely, starting
from emacs -Q?
I have been able to create a minimal set of init.el and WORK.org which
allows me to reproduce the problem:
1) start Emacs
2) F6 (shortcut f
On 20/05/2023 22:01, Ihor Radchenko wrote:
You can try to bisect your config to identify which part is triggering
the problem. See
https://list.orgmode.org/orgmode/87ee2nlslt.fsf@localhost/ and
https://github.com/Malabarba/elisp-bug-hunter
I have been able to create a minimal set of init.el and
Hello
I've come across what seems to be a bug in org-element-cache handling.
To reproduce:
1) create a level 1 heading (in my case: "CAPTURE") and a level 2 heading
(in my case: "CAPTURE-TEST")
2) create a similar template to file tasks under a level-2 heading:
("x" "Todo (test)" entry
(file+olp
On 20/05/2023 22:01, Ihor Radchenko wrote:
You can try to bisect your config to identify which part is triggering
the problem. See
https://list.orgmode.org/orgmode/87ee2nlslt.fsf@localhost/ and
https://github.com/Malabarba/elisp-bug-hunter
FWIW, I just got the following message at startup:
--
On 20/05/2023 22:01, Ihor Radchenko wrote:
You can try to bisect your config to identify which part is triggering
the problem. See
https://list.orgmode.org/orgmode/87ee2nlslt.fsf@localhost/ and
https://github.com/Malabarba/elisp-bug-hunter
bug hunter hasn't helped at all, maybe I've missed som
/05/2023 18:04, Ihor Radchenko wrote:
Patrick Useldinger writes:
Hello
I've come across what seems to be a bug in org-element-cache handling.
To reproduce:
1) create a level 1 heading (in my case: "CAPTURE") and a level 2
heading (in my case: "CAPTURE-TEST")
2) create a
Hello
I've come across what seems to be a bug in org-element-cache handling.
To reproduce:
1) create a level 1 heading (in my case: "CAPTURE") and a level 2
heading (in my case: "CAPTURE-TEST")
2) create a similar template to file tasks under a level-2 heading:
("x" "Todo (test)" entry
(file
