Mark Barton <mbarto...@gmail.com> writes:
>>> 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)
> ...
> Got it to occur in org-agenda-log-mode C-c a a l
>
> Debugger entered--entering a function:
> * org-element-at-point()
> org--collect-keywords-1(("SETUPFILE" "FILETAGS" "TAGS") ("ARCHIVE"
> "CATEGORY" "COLUMNS" "PRIORITIES") nil
> ("/Users/bartm002/Documents/org/Work_Projects.org") nil)
> org-collect-keywords(("FILETAGS" "TAGS") ("ARCHIVE" "CATEGORY" "COLUMNS"
> "PRIORITIES"))
> org-set-regexps-and-options(tags-only)
>
> org-agenda-prepare-buffers(("/Users/bartm002/Documents/org/Work_Projects.org"
> "/Users/bartm002/Documents/org/Bookmarks.org"
> "/Users/bartm002/Documents/org/DailyPlans.org"
> "/Users/bartm002/Documents/org/Personal.org"
> "/Users/bartm002/Documents/org/Today.org"
> "/Users/bartm002/Documents/org/diary.org"
> "/Users/bartm002/Documents/org/goals.org"
> "/Users/bartm002/Documents/org/python_notes.org"
> "/Users/bartm002/Documents/org/refile.org"))
> org-agenda-prepare("Day/Week")
This is perfectly normal.
If you try "e (current-buffer) RET" inside the debugger, you will end up
in an Org file.
There is a reason why I asked to debug display-warning rather than
org-element-at-point itself. What you need to catch is what is calling
org-element-at-point in inappropriate place.
--
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
