From: Mark Barton <mbarton98@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [BUG] Warning (org-element): ‘org-element-at-point’ cannot be used in non-Org buffer #<buffer *Org Agenda*> (org-agenda-mode) [9.7.11 (release_9.7.11 @ /Applications/Emacs.app/Contents/Resources/lisp/org/)]
Date: Tue, 21 Jan 2025 15:06:30 -0800 [thread overview]
Message-ID: <194479CA-A977-48AB-AF68-8FF6DE05D9C8@gmail.com> (raw)
In-Reply-To: <87y0z3q4f9.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 902 bytes --]
> On Jan 21, 2025, at 12:48 PM, Ihor Radchenko <yantar92@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
[-- Attachment #2: Type: text/html, Size: 4093 bytes --]
next prev parent reply other threads:[~2025-01-21 23:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 20:26 [BUG] Warning (org-element): ‘org-element-at-point’ cannot be used in non-Org buffer #<buffer *Org Agenda*> (org-agenda-mode) [9.7.11 (release_9.7.11 @ /Applications/Emacs.app/Contents/Resources/lisp/org/)] Mark Barton
2025-01-21 20:48 ` Ihor Radchenko
2025-01-21 23:06 ` Mark Barton [this message]
2025-01-22 1:09 ` Mark Barton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=194479CA-A977-48AB-AF68-8FF6DE05D9C8@gmail.com \
--to=mbarton98@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).