Re: How global is a define-global-minor-mode mode?

[David Kastrup]

Chong Yidong <address@hidden> writes:

> Richard Stallman <address@hidden> 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.

Uh, wouldn't the file to require be load-file-name at the time
define-global-minor-mode is loaded or executed via autoload?

-- 
David Kastrup