From: Ihor Radchenko <yantar92@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 57972@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#57972: 29.0.50; Autoloaded function raises (void-function org-element-cache-reset) when called within major-mode body
Date: Wed, 21 Sep 2022 20:32:10 +0800 [thread overview]
Message-ID: <CACnOyigm7bLGdMoO1riPYq5166XF4FcOd2pOz_=1KKZ2iiX_wA@mail.gmail.com> (raw)
In-Reply-To: <87k05w6hw3.fsf@gnus.org>
[-- Attachment #1: Type: text/plain, Size: 664 bytes --]
>
> > You have some confusing stuff in org.el -- you have a
>
> > (declare-function org-element-cache-reset "org-element" (&optional all))
>
> > to suppress warnings in org.el about that function, but
> > org-element-cache-reset should be in org-loaddefs, which org.el loads
> > already, so it should be unnecessary.
The declare statement is there for a single reason---to pacify native-comp
warnings.
If it isn't unnecessary, then something else is going wrong somewhere,
> I'd have thought? But I haven't tried debugging further.
>
I removed the declare statement. The bug persists. Also,
org-element-cache-reset is present in org-loaddefs.el
Best,
Ihor
[-- Attachment #2: Type: text/html, Size: 1147 bytes --]
next prev parent reply other threads:[~2022-09-21 12:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 8:33 bug#57972: 29.0.50; Autoloaded function raises (void-function org-element-cache-reset) when called within major-mode body Ihor Radchenko
2022-09-21 11:35 ` Eli Zaretskii
2022-09-21 11:41 ` Ihor Radchenko
2022-09-21 11:55 ` Lars Ingebrigtsen
2022-09-21 12:08 ` Ihor Radchenko
2022-09-21 12:17 ` Lars Ingebrigtsen
2022-09-21 12:32 ` Ihor Radchenko [this message]
2022-09-21 12:46 ` Eli Zaretskii
2022-09-21 13:00 ` Ihor Radchenko
2022-09-21 13:14 ` Eli Zaretskii
2022-09-21 13:19 ` Ihor Radchenko
2022-09-21 14:04 ` Eli Zaretskii
2022-09-21 14:10 ` Ihor Radchenko
2022-09-21 14:27 ` Eli Zaretskii
2022-09-21 14:51 ` Ihor Radchenko
2022-09-21 15:49 ` Eli Zaretskii
2022-09-23 2:10 ` Ihor Radchenko
2022-09-23 7:14 ` Eli Zaretskii
2022-09-23 21:13 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-25 2:43 ` Bastien
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACnOyigm7bLGdMoO1riPYq5166XF4FcOd2pOz_=1KKZ2iiX_wA@mail.gmail.com' \
--to=yantar92@gmail.com \
--cc=57972@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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.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).