Re: new text property

["Stephen J. Turnbull" <stephen@xemacs.org>]

>>>>> "Colin" == Colin Walters <walters@gnu.org> writes:

    Colin> Otherwise, to disable/enable highlighting, you have to
    Colin> track down one of those variables, change it, and then
    Colin> recreate the buffer somehow so the change in the variable
    Colin> takes effect.  Just typing 'M-x font-lock-mode' is tons
    Colin> easier.

Good idea, but we're already heading this way in general with
"behaviors."  Unification we don't have, but the mechanism would allow
arbitrary unifications, I think, just as custom allows you to "set"
variables that don't exist or are a group of related variables..  And
the "recreate buffer somehow" is the main (current) point of the
"behavior feature."

So AFAICT, we can get the immediate effect of the new features through
our general mechanism.  Why reduplicate it ad hoc?

grep for "ben wing + behavior" in xemacs-beta, xemacs-design,
xemacs-patches:  http://list-archive.xemacs.org/$LIST_NAME



-- 
Institute of Policy and Planning Sciences     http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba                    Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
 My nostalgia for Icon makes me forget about any of the bad things.  I don't
have much nostalgia for Perl, so its faults I remember.  Scott Gilbert c.l.py