Re: font-lock: FSF vs XEmacs
Jake Colman <jake.colman(a)xemacs.org> writes:
HN> Go ahead and tinker! :-)
Our implementarion is vastly different than FSF's. I cannot simply
add the missing function because it makes assumptions about how
other functions (i.e., font-lock-set-defaults) work. Our
implementation of that function is radically different so none of
this can be simply ported from one version to the other.
Well, that's why I said "tinker" rather than "copy and paste".
Having said all that, if I did decide to undertake the
(non-trivial?) effort to implement the font-lock-add-keywords
function, what patch process would I follow?
Mail the patch to xemacs-patches(a)xemacs.org. If the patch meets the
standards of quality (which I have no reason to believe it won't), it
will be accepted and applied to the CVS tree.
This means that I'd have to submit a patch to 21.5, have it
approved, and then recommend it back for 21.4, correct?
Given that it's a new feature, Vin will probably not accept it for
21.4. But you can still ask.
(Also note that there are differences between the font-lock in 21.5
and the one in 21.4.)