> On Jan 21, 2025, at 12:48 PM, Ihor Radchenko <yanta...@posteo.net> wrote: > > May you try to run M-x debug-on-entry RET display-warning RET and > try triggering the warning? Then, you will see a backtrace with the full > information about where the warning is triggered. > > (you can later disable the debugger via M-x cancel-debug-on-entry RET RET)
I jinxed it when I said it was easy to reproduce. Because now even if I put that code back in, it does not display the warning for org-element that has been happening for days. The other things that changed are the org files, but the diffs look like normal marking tasks done and updating repeats. The other thing I ran this morning is (native-compile-prune-cache). I would not expect that to be the source. Please close this out and I will file a new report if it happens again with the debug backtrace. Thanks, Mark Barton
