From xemacs-m  Wed Feb 12 22:24:46 1997
Received: from herald.cc.purdue.edu (herald.cc.purdue.edu [128.210.11.29])
	by xemacs.org (8.8.5/8.8.5) with SMTP id WAA24764
	for <xemacs-beta@xemacs.org>; Wed, 12 Feb 1997 22:24:45 -0600 (CST)
Received: from ppp-x9-16.ecn.purdue.edu by herald.cc.purdue.edu; Wed, 12 Feb 97 23:24:35 -0500
Received: (from somasekh@localhost) by ppp-x9-16.ecn.purdue.edu (8.8.4/8.6.12) id XAA00384; Wed, 12 Feb 1997 23:22:55 -0500
Date: Wed, 12 Feb 1997 23:22:55 -0500
Message-Id: <199702130422.XAA00384@ppp-x9-16.ecn.purdue.edu>
From: Dinesh Somasekhar <somasekh@ecn.purdue.edu>
To: Jeff Miller <jmiller@bay1.bayserve.net>
Cc: beta-list <xemacs-beta@xemacs.org>
Subject: Re: compressed .el files
In-Reply-To: <Pine.SUN.3.95.970212200318.22062D-100000@bay1.bayserve.net>
References: <m2914ter5w.fsf@altair.xemacs.org>
	<Pine.SUN.3.95.970212200318.22062D-100000@bay1.bayserve.net>
Reply-To: somasekh@ecn.purdue.edu
X-URL: http://albrecht.ecn.purdue.edu/~somasekh
X-Organization: Purdue University
X-face:  57,u^#nsk>2N2INb(Afe~^~B}j[t7+B)>u]%DYS:\XA8yL6?[*<0"yBBb@*u/e@K#F6?Fi5
 WB?GMJvJPt$5W0bRNZ{dH%ybQO%$]M)b~_G[!*0"[82&2t[3o{EQB87/0J@AtN6@cz1zM_FD1~{maV
 ;qd6T/s(+&j&QJ"zv5'GQU%10P\R)}aW1xq3(;U<M}8W^~Y:4M9cnj"M+R9_FKM%E[HEyle7['_!|i
 (


 I use the following simple shell-script

#!/bin/csh -f
set dir=/usr/local/lib/xemacs-19.15-b92/lisp/
foreach file ( `find $dir -type f -name '*.el' -print` )
if ( -e ${file:r}.elc ) then
echo "Compressing $file" 
gzip --best $file
endif
end

Does this do the job.

"Jeff" == Jeff Miller <jmiller@bay1.bayserve.net> writes:

 > On 12 Feb 1997, Steven L Baur wrote:

 >> It shouldn't affect loading time at all, though I would like to
 >> see compression of .elcs at some point which will affect loading
 >> time.

 > I experimented with this at one time, but once I compressed the
 > .elcs, I couldn't startup XEmacs.  I don't recall the exact error
 > but I think it was related to the fact that I had compressed all
 > the .elcs.  they're are most likely some that should remain
 > uncompressed until after something like "crypt" is loaded.  I don't
 > remember the exact numbers, but I don't think compressing elcs
 > bought me a significant amount of space.

 >> I backed away from the info compression patch, and deferred the
 >> .el compression patch because of coding system problems with
 >> compressed files (see the recent messages about jka-compr).  If
 >> the info files are compressed you cannot read the Japanese
 >> documentation and that is a Bad Thing.
 >> 
 >> What I'd like to see instead is some kind of compact script
 >> optionally run after installation to do the equivalent of what the
 >> installation patches did.  Would you consider this to be an
 >> acceptable solution?

 > yes.

 > In fact this may be a better solution. Compressing the .el files
 > can be quite time consuming.  At least on my 40M 486 it is. :)

 > Would you like me to try writing this script or do you already have
 > something in mind?




--
Dinesh Somasekhar

