From: Alan Mackenzie <acm@muc.de>
To: "markusffm@fn.de" <markusffm@fn.de>
Cc: Colin Baxter <m43cap@yandex.com>, 33602@debbugs.gnu.org
Subject: bug#33602: 27.0.50; Compiling no file at
Date: Fri, 7 Dec 2018 13:43:27 +0000 [thread overview]
Message-ID: <20181207134327.GA7949@ACM> (raw)
In-Reply-To: <20181206215832.GA23102@INDRA>
Hello, Markus.
On Thu, Dec 06, 2018 at 22:58:33 +0100, markusffm@fn.de wrote:
> >Could you please tell us whether your .emacs (or other initialisation
> >file) performs byte compilation, and if so, what commands it does this
> >with.
> there is no byte compile during initialization. All the bytecode is
> untouched for years; without problems until recently.
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!
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2018-12-07 13:43 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 [this message]
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
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
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=20181207134327.GA7949@ACM \
--to=acm@muc.de \
--cc=33602@debbugs.gnu.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).