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

Previous Next

Package: emacs;

Reported by: markusffm <at> fn.de

Date: Mon, 3 Dec 2018 19:24:02 UTC

Severity: normal

Found in version 27.0.50

Done: Alan Mackenzie <acm <at> muc.de>

Bug is archived. No further changes may be made.

Full log


Message #59 received at 33602 <at> debbugs.gnu.org (full text, mbox):

From: Alan Mackenzie <acm <at> muc.de>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: rgm <at> gnu.org, markusffm <at> fn.de, 33602 <at> debbugs.gnu.org, m43cap <at> yandex.com
Subject: Re: bug#33602: 27.0.50; Compiling no file at
Date: Fri, 7 Dec 2018 20:06:59 +0000
Hello, Eli.

On Fri, Dec 07, 2018 at 21:52:48 +0200, Eli Zaretskii wrote:
> > Date: Fri, 7 Dec 2018 19:27:07 +0000
> > Cc: Glenn Morris <rgm <at> gnu.org>, markusffm <at> fn.de, 33602 <at> debbugs.gnu.org,
> >   m43cap <at> yandex.com
> > From: Alan Mackenzie <acm <at> muc.de>

> > Yes.  cl--generic-get-dispatcher calls byte-compile directly.  It calls
> > it on a generated lambda form.  Do we still need to do this nowadays?  I
> > thought the byte compiler had been enhanced to detect and compile such
> > forms automatically.

> I'd ask a different question altogether: now that we know this comes
> from loading generics, why is that entry in compilation log a problem?
> Who cares what the byte compiler says as part of its normal operation,
> and why should we consider that "a bug"?

I still think it's a problem.  It irritates people.

The actual wording of the message "Compiling no file at <time>" is
unclear.  Certainly to a German speaker, it reads identically to "Not
compiling a file at <time>" - why are we reporting on what we're not
doing?  What's really meant is "compiling something, but it's not in a
file".

The message is not in response to a user action - it's Emacs's internal
processing.  The user requested a file to be loaded, not compiled.

The message is content free.  It fails to identify what's being
compiled.  (This could be fixed easily in bytecomp.el.)

Guessing from Markus (the OP)'s post, it seems that the *Compile-Log*
buffer is the current buffer at start up time.  Who needs that?

So, yes, I think it's a bug.

-- 
Alan Mackenzie (Nuremberg, Germany).




This bug report was last modified 6 years and 222 days ago.

Previous Next


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