From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [BUG] org-mouse is activated without explicit require
Date: Tue, 13 Dec 2022 21:32:54 +0700 [thread overview]
Message-ID: <tna2em$13no$1@ciao.gmane.io> (raw)
In-Reply-To: <87359jeikz.fsf@localhost>
On 13/12/2022 16:52, Ihor Radchenko wrote:
> Max Nikulin writes:
>
>>> We have `org-modules' that can handle calling `org-link-set-parameters'.
...> We can simply process 'ol-* in `org-modules' specially.
I do not consider it is a good idea. Third party packages may call
`org-link-set-parameters' as well. That is why I would prefer a more
general approach of package activation.
> The original issue reported in this thread is actually strange - we have
> no single autoload cookie in org-mouse.el. May it be something to do
> with the new Emacs autoload generation?
I do not think it is something new. Even in Emacs-26
`generate-file-autoloads' adds
(if (fboundp 'register-definition-prefixes)
(register-definition-prefixes "org-mouse" '("org-")))
to org-loaddefs.el. The function is called for all sources by
`org-make-org-loaddefs' (defined in mk/org-fixup.el).
next prev parent reply other threads:[~2022-12-13 14:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-11 3:25 [BUG] org-mouse is activated without explicit require Matt Lundin
2022-12-11 3:49 ` Greg Minshall
2022-12-11 4:38 ` Samuel Wales
2022-12-11 9:45 ` Ihor Radchenko
2022-12-11 14:49 ` Autoloading side effects (was: Re: [BUG] org-mouse is activated without explicit require) Max Nikulin
2022-12-12 10:25 ` Ihor Radchenko
2022-12-12 16:20 ` Max Nikulin
2022-12-13 9:52 ` Ihor Radchenko
2022-12-13 14:32 ` Max Nikulin [this message]
2022-12-14 9:59 ` [BUG] org-mouse is activated without explicit require Ihor Radchenko
2022-12-12 15:42 ` Autoloading side effects (was: Re: [BUG] org-mouse is activated without explicit require) Matt Lundin
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='tna2em$13no$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--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).