Mats Lidell writes:
>>>>> Stephen J Turnbull <stephen(a)xemacs.org>
I'm getting more convinced that upgrading existing packages in
tree. even introducing new packages, is the right tool to use.
Of course. But remember what started this thread: a developer who was
having trouble using XEmacs with the packages he wanted.
Most of all I think it is much easier than to introduce core
functionality in isolation.
Problem is, Emacsen in general don't have "isolation", and GNU Emacs
is way worse than XEmacs on this ground. We need both approaches, or
we'll just cruftify rapidly. Most of the actual development work I've
done on XEmacs has been to fix *shit* ported from GNU Emacs hastily,
just enough to work for the developer involved, who typically then
disappears. (To be honest, most of it was reasonable in GNU, it was a
porting job that didn't account for the real technical differences
between XEmacs and GNU, but some of it already was pretty icky.)
I agree with your assessment that we'll make a lot of progress by
upgrading packages, and I don't want to discourage anyone from doing
that. But let's at least pray for some folks who want to do generic
syncs and true ports of Emacs concepts to XEmacs code.
We had a recent gnus update. What other packages do you think are
falling behind and needs to be upgraded?
All of them. ;-) I'm currently working on VM, off and on, lately more
off than on.
XEmacs-Beta mailing list