From: Pierre Lorenzon <devel@pollock-nageoire.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Corrupted byte compiled files
Date: Wed, 30 May 2012 08:54:15 +0200 (CEST) [thread overview]
Message-ID: <20120530.085415.424292590.devel@pollock-nageoire.net> (raw)
In-Reply-To: <jwv7gvuoms9.fsf-monnier+gnu.emacs.help@gnu.org>
From: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Corrupted byte compiled files
Date: Tue, 29 May 2012 14:39:09 -0400
>> Certain of my .el files are incorrectly compiled. See the .elc
>> file with a long name.
>
> Indeed, I can reproduce it here, and also with Emacs-23.
Does that mean that none never tried to compile file with
long name before .... or that the problem does not come
exclusively from the length of the name ....
> I don't have time to dig into it now, tho, so please M-x
> report-emacs-bug so it doesn't get lost.
OK I'll do that. But since I now know that there is really a
problem I'll have a look at the byte compiling engine
code. Maybe I can discover where is th problem ....
Thanks
Pierre
>
>
> Stefan
next prev parent reply other threads:[~2012-05-30 6:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1848.1338298974.855.help-gnu-emacs@gnu.org>
2012-05-29 18:39 ` Corrupted byte compiled files Stefan Monnier
2012-05-30 6:54 ` Pierre Lorenzon [this message]
2012-05-31 11:43 ` Tassilo Horn
[not found] ` <mailman.2011.1338480750.855.help-gnu-emacs@gnu.org>
2012-05-31 17:46 ` Johan Bockgård
2012-05-31 18:56 ` Tassilo Horn
2012-06-01 6:51 ` Pierre Lorenzon
2012-05-29 13:25 Pierre Lorenzon
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=20120530.085415.424292590.devel@pollock-nageoire.net \
--to=devel@pollock-nageoire.net \
--cc=help-gnu-emacs@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.
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).