unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
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: Fri, 23 Sep 2022 10:10:32 +0800	[thread overview]
Message-ID: <871qs2alif.fsf@localhost> (raw)
In-Reply-To: <83v8pgu3rf.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

>   (or (eq this-command 'eval-buffer)  <<<<<<<<<<<<<<<<<<<<<
>       (condition-case nil
> 	  (load (concat (file-name-directory load-file-name)
> 			"org-loaddefs")
> 		nil t nil t)
> 	(error
> 	 (message "WARNING: No org-loaddefs.el file could be found from where org.el is loaded.")
> 	 (sit-for 3)
> 	 (message "You need to run \"make\" or \"make autoloads\" from Org lisp directory")
> 	 (sit-for 3))))
>
> explicitly avoids loading org-loaddefs.el if org.el was loaded via
> eval-buffer.  Which is exactly the case here, isn't it, and explains
> why the loaddefs aren't loaded?
>
> So now the question becomes: why does org.el treat eval-buffer in this
> special way?  Perhaps because of byte-compilation or something?

I have no clue. I will ask Bastien (he authored this piece of code).

I hence see this Emacs bug report as resolved (it is not an Emacs bug).

Side question: Could you point me towards documentation on how to
properly do autoloading in Emacs packages? Maybe Org is doing things
wrongly?

-- 
Ihor Radchenko,
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapay.com/org-mode,
or support my work at https://liberapay.com/yantar92





  reply	other threads:[~2022-09-23  2:10 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
2022-09-21 14:51                   ` Ihor Radchenko
2022-09-21 15:49                     ` Eli Zaretskii
2022-09-23  2:10                       ` Ihor Radchenko [this message]
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=871qs2alif.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=57972@debbugs.gnu.org \
    --cc=eliz@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.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).