Re: Whereto next?

ST> Besides the default Unicode support, what features that are ST> /already/ in 21.5 need to be stabilized for /your/ daily needs? I've been mostly ignoring 21.5, but in response to your query I downloaded the latest bits (21.5.28) from the OpenSUSE Build Service and took 'em for a spin. (I also plan to try 21.5 on Solaris, but I haven't gotten to that yet.) For my purposes 21.5 is usable, though I find the redisplay behavior disconcerting. With 21.4 I could tell XEmacs to go do something, and I'd know it was still working on it because the display was frozen. With 21.5 XEmacs frequently gives the visual impression of having finished my request, when in fact it's still working on it. For example, suppose I'm in a dired buffer for ~/xemacs. I enter C-x d BS BS BS BS BS BS BS tmp RET A dired buffer is redrawn in the frame, but I have to look carefully at it, because it's often still the ~/xemacs buffer. Then a moment later the dired buffer for ~/tmp is drawn. But I can't reproduce it on demand, alas. Any troubleshooting tips? I've also run into a few other minor issues which I plan to file bugs on. Should I wait until the issue tracker is back up? ST> Or can we even get "back on track"? What do you all think? I can't speak to core development, but I'm troubled by the situation with packages. Last I checked, the package build is still broken on 21.4. This means it's been broken for something like 6 months now. My understanding is that this is interfering with promoting packages to stable, which I would really like to see happen before I unleash MH-E 8 on the package build. If we want to get back on track, we need to be more prompt in fixing this sort of breakage. mike _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta