[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#33602: 27.0.50; Compiling no file at
From: |
Eli Zaretskii |
Subject: |
bug#33602: 27.0.50; Compiling no file at |
Date: |
Sat, 08 Dec 2018 12:48:12 +0200 |
> Date: Fri, 7 Dec 2018 20:06:59 +0000
> Cc: rgm@gnu.org, markusffm@fn.de, 33602@debbugs.gnu.org, m43cap@yandex.com
> From: Alan Mackenzie <acm@muc.de>
>
> > 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.
They are free not to look ;-)
> The actual wording of the message "Compiling no file at <time>" is
> unclear.
If we want to change the text, it's fine. But removing the log
altogether sounds like too much to me.
- bug#33602: 27.0.50; Compiling no file at, (continued)
- bug#33602: 27.0.50; Compiling no file at, Eli Zaretskii, 2018/12/07
- bug#33602: 27.0.50; Compiling no file at, Alan Mackenzie, 2018/12/07
- bug#33602: 27.0.50; Compiling no file at, Glenn Morris, 2018/12/07
- bug#33602: 27.0.50; Compiling no file at, Eli Zaretskii, 2018/12/07
- bug#33602: 27.0.50; Compiling no file at, Alan Mackenzie, 2018/12/07
- bug#33602: 27.0.50; Compiling no file at, Eli Zaretskii, 2018/12/07
- bug#33602: 27.0.50; Compiling no file at, Alan Mackenzie, 2018/12/07
- bug#33602: 27.0.50; Compiling no file at,
Eli Zaretskii <=
- bug#33602: 27.0.50; Compiling no file at, Alan Mackenzie, 2018/12/08
- bug#33602: 27.0.50; Compiling no file at, Eli Zaretskii, 2018/12/08
- bug#33602: 27.0.50; Compiling no file at, Alan Mackenzie, 2018/12/09
- bug#33602: 27.0.50; Compiling no file at, Eli Zaretskii, 2018/12/09
- bug#33602: 27.0.50; Compiling no file at, Alan Mackenzie, 2018/12/09
- bug#33602: 27.0.50; Compiling no file at, Colin Baxter, 2018/12/07