From: Richard Stallman <rms@gnu.org>
To: emacs-devel@gnu.org
Subject: byte-compiling compressed files
Date: Tue, 14 Aug 2007 19:26:46 -0400 [thread overview]
Message-ID: <E1IL5mg-0000ql-Dr@fencepost.gnu.org> (raw)
You can visit a compressed .el file, but you can't byte compile it.
Do people think it would be a good idea to add such a feature?
------- Start of forwarded message -------
X-Spam-Status: No, score=0.0 required=5.0 tests=UNPARSEABLE_RELAY
autolearn=failed version=3.1.0
Date: Mon, 13 Aug 2007 08:58:01 +0200
From: ESCOUFLAIRE Pierre-Louis <pierre-louis.escouflaire@eurocontrol.int>
MIME-Version: 1.0
To: bug-gnu-emacs@gnu.org
In-Reply-To: <E1IJjA5-00033P-DB@fencepost.gnu.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Subject: Re: Suggestion: elisp files compression
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.
_______________________________________________
bug-gnu-emacs mailing list
bug-gnu-emacs@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnu-emacs
------- End of forwarded message -------
next reply other threads:[~2007-08-14 23:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-14 23:26 Richard Stallman [this message]
2007-08-15 7:09 ` byte-compiling compressed files Mathias Dahl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1IL5mg-0000ql-Dr@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).