Re: Failure building packages (Vin Shelton)
So far as I could tell, behaviors were essentially a means of globally
enabling or disabling a certain feature. Whoever implemented the
feature would write functions for enabling and disabling it, and
register those through `define-behavior'. The behavior can then be
turned on and off through disable- and enable-behavior. That much, at
least, is implemented.
However,it looks like there was going to be a behavior menu (with
functions like behavior-menu-filter defined.) I don't believe there is
such a menu on the default menu-bar in the latest beta.
Sincerely,
Byrel
On Wed, Jan 11, 2012 at 12:15, Mats Lidell <matsl(a)xemacs.org> wrote:
>>>>> Stephen J Turnbull <stephen(a)xemacs.org> writes:
> Using behaviors is the right thing for the future [...]
I haven't heard about behaviors until this thread. (Good to learn
something new every day!)
It seems like it is a kind of framework for packages. Making it easier
to activate and deactivate a package with integration with customize
around the corner.
I also find some examples(?) for mail and mwheel but fail to
understand if those examples can be activated or if they already are
activated. What is the status of behaviors? Is the code working and
ready to be used?
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta