From: Chong Yidong <cyd@stupidchicken.com>
To: rms@gnu.org
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: How global is a define-global-minor-mode mode?
Date: Sun, 28 Jan 2007 10:47:28 -0500 [thread overview]
Message-ID: <873b5vtapb.fsf@stupidchicken.com> (raw)
In-Reply-To: <E1HB4g5-00069d-Jp@fencepost.gnu.org> (Richard Stallman's message of "Sun\, 28 Jan 2007 02\:42\:17 -0500")
Richard Stallman <rms@gnu.org> writes:
> > Not really: if the global minor mode is autoloaded, then :require is
> > a nuisance,
>
> > I don't follow. Could you explain why it is a nuisance?
>
> The :require thingy is a risk: if you move the definition of the mode to
> another file, then the user's customizations will be broken (it happened
> with global-font-lock-mode).
>
> It seems that you are saying the risk is that the :require has to
> specify the file name, so if you move the definition to another file,
> the :require argument will be wrong.
>
> If the :require is generated automatically, perhaps it would never be
> wrong.
The only way for Emacs to know which source file to :require, for a
third-party package, is to look at the custom-set-variables
declaration in .emacs. Therefore, the only way your suggestion can
work is for define-global-minor-mode to somehow put this information
in .emacs. If you move the source file to a different location there
is no way for .emacs to be automatically updated.
So there's no sane way to handle this automagically.
next prev parent reply other threads:[~2007-01-28 15:47 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 18:35 How global is a define-global-minor-mode mode? Lennart Borgman
2006-12-25 0:43 ` Richard Stallman
2006-12-29 15:44 ` Richard Stallman
2006-12-29 17:21 ` Lennart Borgman (gmail)
2006-12-30 6:23 ` Richard Stallman
2006-12-30 10:57 ` Lennart Borgman (gmail)
2006-12-31 1:46 ` Richard Stallman
2006-12-31 2:27 ` Lennart Borgman (gmail)
2006-12-31 22:13 ` Richard Stallman
2007-01-03 0:18 ` Johan Bockgård
2007-01-03 21:11 ` Richard Stallman
2007-01-20 19:34 ` Chong Yidong
2007-01-21 22:27 ` Richard Stallman
2007-01-21 23:11 ` Stefan Monnier
2007-01-22 9:04 ` Richard Stallman
2007-01-22 14:55 ` Stefan Monnier
2007-01-23 20:55 ` Richard Stallman
2007-01-23 23:00 ` Stefan Monnier
2007-01-23 23:59 ` Lennart Borgman (gmail)
2007-01-24 1:15 ` Stefan Monnier
2007-01-24 19:29 ` Lennart Borgman (gmail)
2007-01-25 4:57 ` Stefan Monnier
2007-01-25 8:56 ` Lennart Borgman (gmail)
2007-01-25 19:27 ` Stefan Monnier
2007-01-25 21:47 ` Lennart Borgman (gmail)
2007-01-25 23:56 ` Lennart Borgman (gmail)
2007-01-26 4:34 ` Stefan Monnier
2007-01-27 19:43 ` Chong Yidong
2007-01-26 4:35 ` Stefan Monnier
2007-01-28 7:42 ` Richard Stallman
2007-01-28 7:42 ` Richard Stallman
2007-01-28 15:47 ` Chong Yidong [this message]
2007-01-28 16:37 ` David Kastrup
2007-01-28 19:53 ` Chong Yidong
2007-01-29 4:32 ` Stefan Monnier
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=873b5vtapb.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@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).