[AC carbon] Synch of Carbon branch to 21.5.13

APPROVE COMMIT Carbon This synchs up the code in the Carbon branch from 21.5.9 (more or less) to 21.5.13 (exactly, except for the Carbon-specific code). I'm going to try to keep this synched every couple of weeks from now on; I believe it will build correctly as an ordinary X application on Mac OS X. It would be helpful if some testers would use the Carbon branch for their X builds in 21.5 as well as their Carbon builds, so that we can weed out any problems due to the new code and build targets for Carbon. WARNING WARNING WARNING This is so far a purely textual synch, and builds on Linux/i386 (!), and that's all the testing that has been done so far. The only reason I'm actually posting this is in hope that people using the Carbon build will think twice about cvs updating if they notice the commits. If you're the brave bleeding edge type, please do update, build, and tell us about the problems. If not, you might want to wait a bit, or use the Carbon_pre_21_5_13_merge tag to get the (few) changes from Pitts Jarvis's 21.5.9 release that are in the XEmacs repository. Note that this new code includes a few regex fixes and new code from Ben that is intended to make fiddling with your system stack limit unnecessary, as well as lots of destabilizing new stuff from all the usual suspects. This is a pretty big change from the 21.5.9 code base Carbon builds have used until now, although the Carbon features themselves have changed very little yet. If you want to know exactly what changed, cvs diff -uN -r Carbon_pre_21_5_13_merge -r Carbon_post_21_5_13_merge for the merged changes to the Carbon branch (about 6MB of diff), and cvs diff -uN -r r21-5-13 -r Carbon_post_21_5_13_merge for the Carbon changes to the 21.5.13 code base, will give you all the details you ever wanted to know but were afraid to ask! -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.