|--==> "SJT" == Stephen J Turnbull <stephen(a)xemacs.org> writes:
>>>>>"SY" == Steve Youngs
<youngs(a)xemacs.org> writes:
SY> I would hardly call it a waste in time.
SJT> Core GNU Emacs people certainly would, and people who are closer to
SJT> the GNU project than to XEmacs probably would. But many of our
SJT> packages come from just those people.
All the more reason to encourage the use of the nifty things that
XEmacs can do. Once they get used to it, you never know, some of them
might switch to XEmacs completely. :-)
SY> If we won't use our stuff, why should anyone else? [1]
SJT> We do, in core, and in packages where the "upstream" maintainer is an
SJT> XEmacs person.
We do believe that extents are better than overlays don't we? In that
case shouldn't we be aiming for 100% use?
SJT> The packages are not "us", they're mostly third-party. In many
cases
SJT> originally developed and still maintained by GNU Emacs people for GNU
SJT> Emacs.
My mature response: So.
SJT> VM does use extents on XEmacs.
OK, now I don't know what you meant when you referred to Kyle. What
was your point? Seems to me like you've shot your own argument. Or
am I missing something?
SJT> But the compatibility API uses the _name_ "overlay", and of course on
SJT> GNU Emacs the VM functionality is implemented using overlays.
Which is fair enough, isn't it?
SY> [1] BTW, when was the last time anyone wrote an XEmacs module?
SY> They sound like a nifty idea to me. I think we should be
SY> encouraging development there too.
SJT> Andrew Begel at UC Berkeley is doing very active development of
SJT> "something" with modules, as is Jerry James ("something
else") at U
SJT> Kansas.
Cool!
--
|---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|