What is the status of 21.5?

SL Baur writes: Oh, just about everything. 1. The long-standing bug in the progress gauge is still there; the only way to be sure not to crash is to disable the widget. 2. Unicode support sucks. 3. Xft support sucks. 4. Carbon support isn't in the mainline yet. 5. Gtk is effectively unsupported (we still require v1). 6. The new GC sucks, at least RAM and CPU. 7. There are infloops or something like them in the regexp engine. 8. Fontlock is still way too slow, partly due to 7, partly due to 9. 9. The stack of extents code is not robust to "large" extents, at least with Mule support. (Eg, putting an extent on (point-min), (point-max) will slow things very badly.) 10. comint needs GNU sync, but this is known to be hard, as we just had to back out the last attempt. 11. We still don't have an all in one tarball. 12. AUCTeX and preview-latex support is a real issue for many people; it seems we can't do that without supporting more of the GNU image API. 13. Mule coding systems suck, and autodetection needs a lot of tuning. 14. Modules don't really work right yet. I think we should go to a model like Python's where .so's and .py's mix interchangably, but that doesn't go with binary packages very well. Elisp eggs would be nice, too (Google for "python eggs"). That's off the top of my head. Do your PostgreSQL support. I don't know about "one true way"; MySQL at least is still way popular in the webapp end of the world. But more SQL support would be a good thing. I have a few desiderata, I've got libneon and libcurl added as modules in a private workspace, and I'd like to see libsvg and expat or libxml supported as modules. We also need to do something with git, which is just LISP in C clothing. It is just dying to be given LISP bindings. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta