Suggestion: elisp files compression

Suggestion: elisp files compression

[ESCOUFLAIRE Pierre-Louis]

Hello,

On installing emacs-22.1, I have noticed that elisp source files are 
compressed on 'make install'.

The problem is that navigating through gzipped elisp source files is 
transparent but byte-compiling them is not (for files with dependencies).

I understant that it is not really one's common to patch an elisp source 
file provided with emacs but should it not be possible to have a 
'--no_compress' (or look-alike) option to the 'configure' script so that 
problem for compilation transparency could be avoided?


Thanks for your concern.

Regards,
Pierre-Louis ESCOUFLAIRE.

____

This message and any files transmitted with it are legally privileged and intended for the sole use of the individual(s) or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by reply and delete the message and any attachments from your system. Any unauthorised use or disclosure of the content of this message is strictly prohibited and may be unlawful.

Nothing in this e-mail message amounts to a contractual or legal commitment on the part of EUROCONTROL, unless it is confirmed by appropriately signed hard copy.

Any views expressed in this message are those of the sender.

Re: Suggestion: elisp files compression

[ESCOUFLAIRE Pierre-Louis]

Hello,

"A picture is sometimes more valuable than 1,000 words", :) then...

The `ediff-util.el.gz' emacs byte-compilation (using the menu item in 
``Emacs-Lisp") reproduces the problem and outputs the following error 
message:

\f
Compiling file /home/esf/emacs-test/ediff-util.el.gz at Mon Aug 13 
08:28:10 2007
ediff-util.el.gz:68:32:Error: Cannot open load file: ediff-init.el


Note that the 'ediff-init.el.gz' file is in the same directory.
Then, what I mean by transparency is that it cannot open the gzipped 
file corresponding to the non-gzipped one.

A bit deeper into `ediff-util.el.gz' (line 68) shows a difference with 
previous lines that use `nil` rather than `'noerror` (column 32) and the 
`load` function description says:

If optional second arg NOERROR is non-nil,
report no error if FILE doesn't exist.


I am not sure to fully understand the meaning of the description (report 
no error = do not report error ?) but this could be a problem from 
NOERROR that should not report an error.


Thanks for your time and concern.

Regards,
Pierre-Louis ESCOUFLAIRE


Richard Stallman wrote:
>     The problem is that navigating through gzipped elisp source files is 
>     transparent but byte-compiling them is not (for files with dependencies).
> 
> I don't really understand what that means.  Could you explain?
> Could you state a precise test case?


____

This message and any files transmitted with it are legally privileged and intended for the sole use of the individual(s) or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by reply and delete the message and any attachments from your system. Any unauthorised use or disclosure of the content of this message is strictly prohibited and may be unlawful.

Nothing in this e-mail message amounts to a contractual or legal commitment on the part of EUROCONTROL, unless it is confirmed by appropriately signed hard copy.

Any views expressed in this message are those of the sender.