Re: Release candidate for XEmacs 21.4.4 / my vacation

APA> If this change turns out to be too risky, I can work with a APA> locally modified 21.4.5. APA> I would like to ask people to actually try it, on Windows and APA> UNIX. Please do. I think that I'm also going to change my bone-lazy ways. I'll start taking patches that are controversial only because of my conservatism and apply them to "candidate releases" early. With CVS tags, it will be easier for activists to test. That doesn't mean they won't come back out if I get nervy :-) but it gives them a better test than what I'm currently doing. Stephen> With a little care, it could be a generic solution: the Stephen> package would be "lisp-updates" or some such. APA> I'm not sure I like this. I'm not, either. But I'd really like to get as many of these "is it a bug or a missing feature" decisions off the core engineers' desks as possible, especially the stable engineers. It's wrong for important fixes on some platform to be delayed simply because I am or Vin is worried that they'll have unexpected side effects on another one. It's wrong for Cyrillic users to have to use ugly and limited fonts because of my lack of knowledge of CCL. But I think we do need to make great effort to promote stability. I'd be happy to hear other ideas; this is just one that occurred to me. APA> This would add yet another complication to debugging people's APA> setups who turn to comp.emacs.xemacs, stating: "My XEmacs APA> does not work." APA> In addition to the usual stuff we would have to find whether APA> they run with any or some "lisp-updates". Maybe we should add the feature list to M-x report-emacs-bug. That, in combination with the output of list-packages, would go a long way toward identifying the configuration in use. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."