🚀 go-pugleaf

I would like to suggest integarating compress into emacs so that it won't 
write out info files in plain text.  No matter how cheap monster hard disks
will be (or to some people, already are), saving disk space is never a bad
practice.  In addition, the other face of compress, namely zcat, reads *.Z
very efficiently to stdout, so we have nothing to worry.
 
I have got quite a few ways to use *.Z format info files inside of emacs
18.55 on my i386 box running ESIX V R3.2 RevD, I was in need of such feature
because I only had (still have, I am a poor grad) 110 Meg at my disposal,
and before compression, info files ate up 20+ megs!

Even AT&T would use these silly *.z (ie.packed) preformatted man pages, 
remember?  FSF ought to do better.  Let's use *.Z which is much smaller than
*.z typically.

Another thing, my OS vendor won't start shipping Sysv R4.0 until April, so
now I have to live with R3.2 and coff stuff.  Can someone who has got other
flavor(s) of UNIX/386 V R4.x share your experience about porting Gnu       
packages in general?   I remember GNU has a prounced BSD bias (sorry about
this word, no bad implication here) and in R4.x, is porting life easier?
Now that COFF is gone forever, how is the new R4.x file format?  Any new
headaches?  Do you need any new patches like those available at osu for
COFF to make the new AT&T file format work with gas, gdb?  

Finally, I wonder whether anyone has made gprof working for UNIX/386 V R3.2
in general and ESIX V in particular?  If so, would you please mail me a 
patch or post?  
 
Regards,
 
Chin Fang
Mechanical Engineering Department
Stanford University
fangchin@portia.stanford.edu