Re: PLEASE TEST XEmacs 21.4.9 "Informed Management" Release Candidate 1

Stephen> Please test the release candidate. Stephen> Use "cvs update -r r21-4-9rc1" to get the RC sources. I hope to get Stephen> tarballs up tomorrow or Monday my time. For now CVS is up-to-date and Stephen> so I'm announcing for those testers who use CVS. Stephen> Use "cvs update -r candidate-21-4" to get the latest and greatest. Stephen> Don't even expect checkouts on this tag to build; I commit what I have Stephen> when I feel like it. Mostly it should work, but if it doesn't, take Stephen> two aspirin and cvs update in the morning. ;-) Stephen> "Release candidate" is something of a misnomer, there are a number of Stephen> patches in the queue that I probably will apply, and I really hope Stephen> that the syntax.c problems (aka "font-lock slows") will get fixed for Stephen> 21.4.9. We'll see .... Anyway, expect at least one more candidate Stephen> before 21.4.9. Stephen> TESTING PROCEDURE Stephen> 1. Get the sources. Stephen> 2. Configure as usual, and if you're feeling especially chipper, try Stephen> several variants that are new and different. Stephen> 3. Use M-x build-report to report each build and any problems. If you Stephen> have problems, please CC xemacs-beta. Successful builds can just Stephen> go to xemacs-buildreports. Stephen> 4. Test and send reports to xemacs-beta, positive or negative. hey stephen just thought i would let you know i have been using r21-4-9rc1 since you sent this email and i havent had any problems yet :) havent noticed anything weird either Stephen> WHAT TO TEST Stephen> 1. I've included the work done by Andy and Nix to support vertical Stephen> positioning of glyphs and some other redisplay hacking needed to Stephen> support preview-latex. This is most definitely a feature, and Stephen> therefore I really should not include it in 21.4. Please try Stephen> preview-latex (http://preview-latex.sourceforge.net/ IIRC). The more Stephen> reports and the more detail I get, the more likely I am to include Stephen> it. Maybe not 21.4.9, maybe 21.4.10. Stephen> Please beat hard on this one. preview-latex is really cool and I Stephen> would like to support it in 21.4. just downloading preview-latex, will let you know how it goes Stephen> 2. I've included Andy's revert-buffer optimization. The idea is to Stephen> compare the buffer text to the file contents, and not redo expensive Stephen> buffer analysis (eg, font-lock and semantic bovination) if the text is Stephen> the same. Stephen> There are reports on 21.5 that this code trashes markers and extents Stephen> when you revert. This is probably fixed already, but please be on the Stephen> watch for such problems, and any anomolies when you revert. Again, Stephen> this code may not make it in to 21.4.9. havent noticed any strangeness here either Stephen> 3. Builds on Linux PPC, OpenBSD, and any 64-bit platforms would be Stephen> nice, I've added some configure tests and s&m pervection to support Stephen> those. MacOS/X Darwin is already in 21.4.8, but build reports on that Stephen> platform would be nice, too. i want a G4 Powerbook now :( Stephen> The OpenBSD changes include detection of a OpenBSD weirdness where Stephen> they rename libcurses as libtermcap or something like that. I think Stephen> it's well-guarded by an "if [ opsys = openbsd ]", but be on the Stephen> lookout for configure failures and runtime weirdness for TTY stuff. hmm maybe i can install OpenBSD on my server :) and test XEmacs need that cable connection :( -- XEmacs Advocate | Do not try the patience of Wizards, FreeBSD Devote | for they are subtle and quick to anger. Perl Hacker | - Elric (Technomage) , Babylon 5. Apache God | <mailto:rendhalver＠xemacs.org>