From: Bob Newell <bobnewell@bobnewell.net>
To: emacs-orgmode@gnu.org
Subject: Re: What might ‘org-element-at-point’ be doing in *scratch*?
Date: Tue, 04 Jun 2024 16:36:04 -1000 [thread overview]
Message-ID: <c5sqjs01e.psgxcls4cq@any0a.3adh4k.com> (raw)
In-Reply-To: <87bk4h5aai.fsf@christianmoe.com> (Christian Moe's message of "Tue, 04 Jun 2024 11:15:03 +0200")
Christian Moe <mail@christianmoe.com> writes:
> Hi,
>
> After upgrading to 9.7.1 on Emacs 27.1, I get a curious warning on Emacs
> start-up:
>
> "Warning (org-element): ‘org-element-at-point’ cannot be used in non-Org
> buffer #<buffer *scratch*> (fundamental-mode)"
>
> It does not happen with 'emacs -Q', but it also did not happen before
> the upgrade, so I don't know what in my configuration now triggers it,
> or why anything would want to do this.
>
> Anyone else seeing this?
I also started to see this. I too traced it to some of my own
coding where I was doing some fancy reformatting of the "*Org
Agenda*" buffer with a definition of org-agenda-prefix-format
that called my user function with an argument including
(org-get-outline-path). This now gives the above warning
because *Org Agenda* is not an org buffer per se.
I worked around it by removing the custom code which was
pretty awkward in any case. It does however leave open the
question about whether there are or are not legitimate cases
for org-element-at-point in buffers which are not org buffers
but present summary or custom views of org material like the
agenda.
--
Bob Newell
Honolulu, Hawai`i
- Via GNU-Linux/Emacs/Gnus/BBDB
next prev parent reply other threads:[~2024-06-05 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 9:15 What might ‘org-element-at-point’ be doing in *scratch*? Christian Moe
2024-06-04 10:13 ` Ihor Radchenko
2024-06-04 10:34 ` Christian Moe
2024-06-05 2:36 ` Bob Newell [this message]
2024-06-05 14:40 ` Ihor Radchenko
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=c5sqjs01e.psgxcls4cq@any0a.3adh4k.com \
--to=bobnewell@bobnewell.net \
--cc=emacs-orgmode@gnu.org \
/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).