From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: markusffm@fn.de, 33602@debbugs.gnu.org, m43cap@yandex.com
Subject: bug#33602: 27.0.50; Compiling no file at
Date: Fri, 7 Dec 2018 18:59:25 +0000 [thread overview]
Message-ID: <20181207185925.GF7949@ACM> (raw)
In-Reply-To: <83ftv95ga0.fsf@gnu.org>
Hello, Eli.
On Fri, Dec 07, 2018 at 20:43:35 +0200, Eli Zaretskii wrote:
> > Date: Fri, 7 Dec 2018 18:11:12 +0000
> > From: Alan Mackenzie <acm@muc.de>
> > Cc: Colin Baxter <m43cap@yandex.com>, "markusffm@fn.de" <markusffm@fn.de>,
> > 33602@debbugs.gnu.org
> > > and one of the next days Angelo reported
> > > > Compiling no file at Thu Dec 6 09:46:33 2018
> > > From Angelo's init file I traced that message back to the presence of
> > > (require 'package)
> > > and removing that removed the message.
> > When I insert that into my .emacs, regardless of whether near the
> > beginning or near the end, I don't get the *Compile-Log* buffer.
> Are you using the master branch? Those problems are specific to the
> master branch, AFAIU.
I am, yes. But I hadn't updated the particular version I was using for
quite some time. I have updated it now.
Now I see the *Compile-Log* buffer with its irritating message regardless
of whether I have (require 'package) in my .emacs or not. ;-(
At least I've got something to work on, now. (That's assuming that
nobody else understands the bug, yet.)
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2018-12-07 18:59 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 [this message]
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=20181207185925.GF7949@ACM \
--to=acm@muc.de \
--cc=33602@debbugs.gnu.org \
--cc=eliz@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).