Nits with the current source trees

Hello all. I'm subscribed again. Now tell me, why are all the historical ChangeLog files not distributed any more? That makes forensic debugging very difficult. The documentation of forward-sexp stinks, but at least the implementation doesn't suck as much as FSF 21.4. I'll make a patch for that once I have a devel environment downloaded. It *must* be documented that forward-sexp can signal an error. The cvs instructions on the web page are wrong. You should say that the .cvspass file must exist before doing any of the documented cvs actions. (touch ~/.cvspass is OK). What is the status on this side of Mac OS X Carbon support? I've had a brief discussion with the author of the prominent patches on the web and the situation is hopeless. I need something to hack on and I need a graphical XEmacs in the Carbon environment. (I don't have very much time on this platform. This box is a present for my wife, but I want it to have a working XEmacs before I hand it over). Excellent job and a pat on the back for 21.4. Andy, I know there were lots of problems getting the tab support into mainline, but I *love* the result. I had problems installing the Microsoft Windows binaries on the XEmacs website on a Thinkpad T-60 running Microsoft Windows XP-SP2, but you know what? I don't care. That machine runs Linux now and XEmacs 21.4 runs *great*. Do we have a WoW mode for editing LUA source files for WoW UI addons? Inquiring minds want to know! -sb _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta