|
From: | Dmitry Gutov |
Subject: | Re: [PATCH] font-core: add font-lock-{enable, disable}-global-for functions |
Date: | Mon, 05 Jan 2015 03:02:15 +0300 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:33.0) Gecko/20100101 Thunderbird/33.0 |
On 01/05/2015 02:44 AM, Stefan Monnier wrote:
Depends what you mean by "derived modes problem". My version of the problem is when activating foo-mode in parent-mode and foo-mode fails to be activated in child-mode.
If you want derived modes to always be affected, you could just as well (aside from backward incompatibility) change `turn-on-font-lock-if-desired' to use `derived-mode-p'.
My version is more complicated: in some cases we might want derived modes to be affected, in others not. A graphical interface for picking the modes and modifiers might turn out to be more confusing than editing the Lisp form.
That's no worse than the current font-lock-global-modes.
It makes to pretence of solving that problem, though. Often that's better than solving a problem halfway (no misconceptions for the user).
[Prev in Thread] | Current Thread | [Next in Thread] |