|
From: | Lennart Borgman (gmail) |
Subject: | Re: How global is a define-global-minor-mode mode? |
Date: | Wed, 24 Jan 2007 00:59:53 +0100 |
User-agent: | Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.9) Gecko/20061207 Thunderbird/1.5.0.9 Mnenhy/0.7.4.666 |
Stefan Monnier wrote:
Isn't it the case that it works if the minor mode function corresponding to the variable is autoloaded? Otherwise, IIRC you need to add a :require to the definition of the minor mode.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).
I have lost my way here, but I did some tests to try to understand. If I use defcustom with a :set function this will be called when the elisp file is loaded. Why can't something similar be done for define-global-minor-mode also? It is a global mode and then :set is passed to defcustom, or?
BTW should not the name be define-globalized-minor-mode as was suggested before?
[Prev in Thread] | Current Thread | [Next in Thread] |