On Wed, 2002-05-01 at 02:47, Steve Youngs wrote:
VS> I've understood that font-lock may be a bit
controversial topic, but
VS> there are a couple of *-faces and the :inherit stuff that might be
VS> useful to have in XEmacs also.
Yeah, that'd be pretty nifty.
Ok, I'll see if I can find time to do a (at least) partial sync soon.
VS> derived.el seems quite different in XEmacs from what it is
VS> which makes it difficult to sync other modes since they seem to be using
VS> it increasingly much and it seems to have some nice goodies. derived.el
VS> is in core now, and a grep to the current source tree reveals that it is
VS> (possibly) only in use in help.el and list-mode.el there. Would it be
VS> possible/useful to move it into xemacs-base?
Anything's possible. But what do we gain from moving a piece of
dumped lisp into the packages?
Well, the ability to actually _use_ the new functionality in packages
without having to worry about backwards compatibility for XEmacsen that
do not have the new stuff. Looking from the packages side, it would not
be too useful to update for example derived.el in XEmacs 21.5 with Emacs
21.2, since packages could still not use it as they have to support 21.1
and 21.4 too. Plus the usual benefits for lisp in packages vs in core;
quicker, better targeted change/bugfix/update cycle etc?
Ah, and for these reasons it would be nice to have font-lock in packages
too, but I see there is some C code (src/font-lock.c) related to it,
might be a trickier one to move? Maybe this is why font-lock is still
in core and not in fsf-compat or xemacs-base though many
font-lock-*-face docs say "It is present only for horrid FSF
By "possible" I meant stuff like what happens if an XEmacs with
dumped/in-core foo.el installs and uses a package with a new version of
foo.el? Warnings? Which version will actually be used? Other
VS> Also, I think an up to date easy-mmode.el should be included
VS> package, preferably xemacs-base. There is a version of it in pcl-cvs,
VS> but IMO that's not the correct place for it, and this version seems
VS> pretty outdated.
Yep, no problem with doing this. I'll move the file then you can sync
Cool. I'll take a look after the move has happened.