Re: Need some bug/version info
David Kastrup <[email protected]>
| Newsgroups | gmane.emacs.auc-tex,gmane.emacs.xemacs.beta |
|---|---|
| Message-ID | <[email protected]> |
Reiner Steib <[email protected]> writes: > There have been a couple of reports about Gnus not working correctly > (infinite loops) on XEmacs 21.4.16 too: > http://thread.gmane.org/gmane.emacs.xemacs.beta/17592 > http://thread.gmane.org/gmane.emacs.gnus.general/59452 > http://thread.gmane.org/gmane.emacs.xemacs.beta/17534 > http://thread.gmane.org/gmane.emacs.xemacs.beta/17437 > > Hopefully these problems are fixed in the upcoming XEmacs 21.4.17. There were quite a few shy regexps in gnus Elisp files IIRC, and gnus would be a candidate for using process filters and similar (which start with fresh regexp data structures). > I agree with David's position. We should not clutter AUCTeX with > workarounds for this particular XEmacs release. We should probably > release AUCTeX 11.55 (a couple of days?) after XEmacs 21.4.17 is > out. I don't think that there is a point in delaying AUCTeX 11.55: the problem is in the font lock code, and earlier AUCTeX versions would show them, too, unless I am mistaken. And earlier AUCTeX releases don't carry a warning against XEmacs 21.4.16 anywhere. So getting AUCTeX out with an appropriate warning (and we can also spice the spec file for RPM files with a conflict for a few releases until the word has spread) would appear to be the correct thing rather sooner than later. I have now to vanish for a concert, but I might release 11.55 this night if everything else is set for it. Even if somebody tells me that the old 11.54 would work without problems with XEmacs 21.4.16, the text corrupting bugs we have in 11.54 don't warrant waiting much longer. Further replies directed to the AUCTeX list again. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum