unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Colin Baxter <m43cap@yandex.com>
To: Markus FFM <markusffm@fn.de>
Cc: , 33602@debbugs.gnu.org
Subject: bug#33602: 27.0.50; Compiling no file at
Date: Tue, 04 Dec 2018 06:52:33 +0000	[thread overview]
Message-ID: <8736rdu6ku.fsf@yandex.com> (raw)
In-Reply-To: <ftvel8mz.fsf@fn.de> (Markus FFM's message of "Mon, 03 Dec 2018 20:20:36 +0100")

Dear Markus
>>>>> Markus FFM <markusffm@fn.de> writes:

    > (is that a late April Fools' Day prank?)  after each restart, a
    > *Compile-log* buffer reports Compiling no file at <any date>

Yes, I get that too. It seems to arise because of some bye-compile
instructions in the emacs-init file. It doesn't arise using emacs -q, as
Glenn has pointed out.

---------- snip

    > seq byte-opt gv compile comint ansi-color ring bytecomp
    > byte-compile cconv cl-loaddefs cl-lib eol-conversion easymenu

Try turning off the effects of the above two lines.

Best wishes,


Colin Baxter
m43cap@yandex.com
---------------------------------------------------------------------
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68  2A27 BBFA 2492 91F5 41C8
---------------------------------------------------------------------
The sole cause of all human misery is the inability of people to sit
quietly in their rooms.  Blaise Pascal, 1670
---------------------------------------------------------------------





  parent reply	other threads:[~2018-12-04  6:52 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 [this message]
     [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
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=8736rdu6ku.fsf@yandex.com \
    --to=m43cap@yandex.com \
    --cc=33602@debbugs.gnu.org \
    --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).