From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: markusffm@fn.de, 33602@debbugs.gnu.org, m43cap@yandex.com
Subject: bug#33602: 27.0.50; Compiling no file at
Date: Sat, 08 Dec 2018 12:48:12 +0200 [thread overview]
Message-ID: <83va4447mb.fsf@gnu.org> (raw)
In-Reply-To: <20181207200659.GI7949@ACM> (message from Alan Mackenzie on Fri, 7 Dec 2018 20:06:59 +0000)
> 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.
next prev parent reply other threads:[~2018-12-08 10:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 19:20 bug#33602: 27.0.50; Compiling no file at Markus FFM
2018-12-03 19:40 ` Glenn Morris
2018-12-04 6:52 ` Colin Baxter
[not found] ` <mailman.5104.1543865051.1284.bug-gnu-emacs@gnu.org>
2018-12-06 13:33 ` Alan Mackenzie
[not found] ` <20181206215832.GA23102@INDRA>
2018-12-07 13:43 ` Alan Mackenzie
2018-12-07 13:52 ` martin rudalics
2018-12-07 14:59 ` Alan Mackenzie
2018-12-07 17:49 ` martin rudalics
2018-12-07 18:11 ` Alan Mackenzie
2018-12-07 18:42 ` martin rudalics
2018-12-07 19:02 ` Alan Mackenzie
2018-12-07 18:43 ` Eli Zaretskii
2018-12-07 18:59 ` Alan Mackenzie
2018-12-07 19:01 ` Glenn Morris
2018-12-07 19:17 ` Eli Zaretskii
2018-12-07 19:27 ` Alan Mackenzie
2018-12-07 19:52 ` Eli Zaretskii
2018-12-07 20:06 ` Alan Mackenzie
2018-12-08 10:48 ` Eli Zaretskii [this message]
2018-12-08 20:07 ` Alan Mackenzie
2018-12-08 20:36 ` Eli Zaretskii
2018-12-09 11:30 ` Alan Mackenzie
2018-12-09 12:43 ` Eli Zaretskii
2018-12-09 13:19 ` Alan Mackenzie
2018-12-07 15:04 ` Colin Baxter
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83va4447mb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33602@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=m43cap@yandex.com \
--cc=markusffm@fn.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.