nbecker> What is the diff between xemacs's in 21.0 and 21.2 series? I've been nbecker> using 21.0b60 for some time. I'm wondering whether to try 21.2. 21.0 is the version that's `about to be released'. Unfortunately, it's been in that state for a while. 21.2 is the experimental version. The big change is a set of performance improvements, especially for Mule users. It was rather unstable 2 betas ago, but things have settled down nicely, and 21.2 is certainly worth trying out now. I personally use XEmacs 21.2 exclusively. Martin

Matthew> Is 21.2 a CVS-only, or are there tarballs? I am working on an NT machine Matthew> and it will be a few weeks before I get my Linux box back to where I Matthew> could try using CVS. But then, I'd nead a tarball to start from anyway Matthew> since rematerializing a whole CVS tree over 56K line is probably too Matthew> slow, yes? Check it out at ftp://ftp.xemacs.org/pub/xemacs/beta/xemacs-21.2 I recommend CVS, though. cvs -z9 -d :pserver:xemacs＠cvs.xemacs.org:/usr/CVSroot checkout -R r21.2.8 xemacs Martin

Gee, never thought of it that way. Nice to know I'm being useful and not just a Luddite of sorts. Kyle Jones wrote: -- Matthew O. Persico http://www.erols.com/mpersico http://www.digistar.com/bzip2

jam> Perhaps I need a little remedial CVS tutorial. Martin> ftp://ftp.xemacs.org/pub/xemacs/beta/xemacs-21.2 jam> 1. Before doing that I can look see how big the tarball is and choose jam> accordingly where to put it. jam> 2. When it arrives I can check the signature to tell me the file is jam> uncorrupted since someone I might know signed it. jam> 3. Before unpacking it I can see what is there and where it will go. jam> 4. I can choose to put it where it won't clobber something that I jam> already have and that works (or least that I know something about). jam> 5. If I run out of space unpacking it I can without too much trouble jam> try again someplace else. If you ALMOST run out of space getting it from CVS, and then do a build, you will run out of space later during the build of the elc and info files. Disk management is inherently non-automatable. Martin> I recommend CVS, though. Martin> cvs -z9 -d :pserver:xemacs＠cvs.xemacs.org:/usr/CVSroot Martin> checkout -R r21.2.8 xemacs jam> At minimum, how can I tell what I'm getting in for. How can I tell jam> how big it is and where will it land. How can I specify where it will jam> land? There doesn't seem to be a way to recursively estimate disk sizes of an exported CVS directory. A rule of thumb is that a CVS tree is only slightly larger than the equivalent exploded tarball from the ftp site without the CVS subdirectories. The really big disk overhead is at the server, as it should be. jam> Where should I go to learn how to do these things? http://cvs.xemacs.org/ http://www.cyclic.com/cvs/info.html Martin