GNU bug report logs - #33602
27.0.50; Compiling no file at

Previous Next

Full log

View this message in rfc822 format

From: martin rudalics <rudalics <at> gmx.at>
To: Alan Mackenzie <acm <at> muc.de>, "markusffm <at> fn.de" <markusffm <at> fn.de>
Cc: Colin Baxter <m43cap <at> yandex.com>, 33602 <at> debbugs.gnu.org
Subject: bug#33602: 27.0.50; Compiling no file at
Date: Fri, 07 Dec 2018 14:52:00 +0100

> Yes.  I put some enhancements into the byte compiler's warning handler
> very recently, and suspect that has triggered some existing problem, and
> that is what you are seeing.
>
> Having grepped Emacs's source, it seems like the byte compiler is the
> only bit that writes "Compiling no file at ..." to the buffer
> *Compile-Log*.  There are quite a few Emacs functions which call the
> byte compiler, even though they are not byte compilations themselves.
>
> Would you be prepared to help us with a bit of debugging?  What would be
> useful is for you to "bisect" your .emacs file.
>
> That is, comment out the second half of it (more or less), start Emacs
> and note whether the silly warning happens.  If it does, comment out the
> last three quarters (more or less) of .emacs, if it doesn't, comment
> out the first quarter.  And so on.
>
> This should quickly home in on the form in your .emacs which is
> triggering the bug in Emacs.  Please tell us what this form is.  It
> would help greatly in solving the problem
>
> @Colin: any chance you could do the same, please.
>
>> Regards M
>
> By the way, would you please leave in the mailing list address as a Cc:,
> so that everybody can see what's happening.  Thanks!

FWIW the problem is in package.el.  Have a look at the fix I just posted.

martin

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.