From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Autoloading side effects (was: Re: [BUG] org-mouse is activated without explicit require)
Date: Sun, 11 Dec 2022 21:49:03 +0700 [thread overview]
Message-ID: <tn4ql0$bu2$1@ciao.gmane.io> (raw)
In-Reply-To: <87iliie0j1.fsf@localhost>
On 11/12/2022 16:45, Ihor Radchenko wrote:
> We cannot do much about Emacs' handling of autoloads, but what we can
> (and should) do is changing org-mouse to become a global minor mode.
> Then, loading org-mouse will cause no side effects.
I am afraid, requirement that loading should not cause side effects is
too strict and it will make usage inconvenient. Examples:
- ol-info calls `org-link-set-parameters'.
- org-protocol installs an advice for `server-visit-files'. (It should
not be necessary, but currently Emacs does not provide a better option.)
However I agree that it is undesired when attempt to call interactive
help causes side effects. I would say that in such cases loading of
packages should be sandboxed and should not propagate to global scope.
next prev parent reply other threads:[~2022-12-11 14:50 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 ` Max Nikulin [this message]
2022-12-12 10:25 ` Autoloading side effects (was: Re: [BUG] org-mouse is activated without explicit require) Ihor Radchenko
2022-12-12 16:20 ` Max Nikulin
2022-12-13 9:52 ` Ihor Radchenko
2022-12-13 14:32 ` [BUG] org-mouse is activated without explicit require Max Nikulin
2022-12-14 9:59 ` 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='tn4ql0$bu2$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).