From: Lars Ingebrigtsen <larsi@gnus.org>
To: Ihor Radchenko <yantar92@gmail.com>
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 14:17:48 +0200 [thread overview]
Message-ID: <87k05w6hw3.fsf@gnus.org> (raw)
In-Reply-To: <87zgetvsj7.fsf@localhost> (Ihor Radchenko's message of "Wed, 21 Sep 2022 20:08:44 +0800")
Ihor Radchenko <yantar92@gmail.com> writes:
>> I'm not at all sure I understand myself. A backtrace here would be
>> helpful.
>
> Debugger entered--entering a function:
> * message("File mode specification error: %s" (void-function
> org-element-cache-reset))
> normal-mode(t)
> after-find-file(nil t)
> find-file-noselect-1(#<buffer bug.org> "/tmp/bug.org" nil nil
> "/tmp/bug.org" (127741036 26))
> find-file-noselect("/tmp/bug.org" nil nil t)
> find-file("/tmp/bug.org" t)
> funcall-interactively(find-file "/tmp/bug.org" t)
> command-execute(find-file)
>
> I generated the backtrace using M-x debug-on-entry org-mode and opening
> bug.org. The backtrace appears at the moment I try to step through
> org-element-cache-reset call inside org-mode.
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.
If it isn't unnecessary, then something else is going wrong somewhere,
I'd have thought? But I haven't tried debugging further.
next prev parent reply other threads:[~2022-09-21 12:17 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 [this message]
2022-09-21 12:32 ` Ihor Radchenko
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k05w6hw3.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=57972@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=yantar92@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.