From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: 57972@debbugs.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 17:27:12 +0300 [thread overview]
Message-ID: <83zgesu7jz.fsf@gnu.org> (raw)
In-Reply-To: <CACnOyijgecMXTtNGWM3v8fbD65a0=VM8urTznKqMFTPN9x+z_g@mail.gmail.com> (message from Ihor Radchenko on Wed, 21 Sep 2022 22:10:24 +0800)
> From: Ihor Radchenko <yantar92@gmail.com>
> Date: Wed, 21 Sep 2022 22:10:24 +0800
> Cc: 57972@debbugs.gnu.org
>
> > I cannot reproduce on stable branch either. Only on main.
>
> Then why do you think this is a problem in the core?
>
> As I said in my first message, I either misunderstand something about autoload or it is some kind of
> Emacs bug.
>
> Note that doing emacs -Q -l /tmp/bug.el vs emacs -Q /tmp/bug.el + eval-buffer yields different results.
> I cannot possibly see how it can be anything to do with Org and I have no clue how to approach debugging
> this.
Fair enough.
Would it help to make the backtrace more detailed? Right now, we
don't see anything between the call to normal-mode and the error. If
you manually "M-x load-file RET files.el RET" before doing
eval-buffer, do you get a more detailed backtrace?
And another thing: do you have any clue (or maybe more than a clue)
what changes in Org wrt what's on the Emacs master branch could have
caused this? If you do, can you show those changes, or point to the
specific places in Org files where those changes can be eye-balled?
next prev parent reply other threads:[~2022-09-21 14:27 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
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 [this message]
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=83zgesu7jz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=57972@debbugs.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.