Re: working on getting XEmacs/GTK to 21.2...

-BP> "Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp&gt; writes: -BP> Why is that not the case for X and Motif then? Or Windows? Who said it wasn't? :^) But we're used to it in those cases. Also, we _are_ using X at least in Custom; Custom buffers under X look better than they do on a TTY, just because of the cheesy graphic widgets. Look, we just spent several months with instability due to the native widgets. At the moment, what I know about GTK+ is that (1) xemacs-gtk spews asserts like crazy, and (2) with Andy's last patch to the lwlib tab control widget apparently stabilizing 21.2 --with-widgets, GTK apps now have the top three spots on my "most-likely-to-crash" list.[1] If you had GTK-ized Custom to show, I'd be tempted enough to keep my mouth shut and go with the Review Board consensus. But without that, it's a major instability when we should be thinking about the next release, and I'm voicing opposition. Just postpone making gtk-xemacs the default until we have a release. Then do it in the new unstable branch. Footnotes: [1] I have no idea whether GTK has anything to do with that, but it's the greatest common divisor among Mozilla, Python-wxwin, and xemacs-gtk. -- 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."