all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: David Landell <david.landell@sunnyhill.email>
Cc: 43651@debbugs.gnu.org
Subject: bug#43651: 27.1; compile.el should not parse its own header for errors
Date: Mon, 28 Sep 2020 15:46:28 +0200	[thread overview]
Message-ID: <87lfguui8b.fsf@gnus.org> (raw)
In-Reply-To: <87blhrzeez.fsf@xwing.i-did-not-set--mail-host-address--so-tickle-me> (David Landell's message of "Sun, 27 Sep 2020 12:45:24 +0200")

David Landell <david.landell@sunnyhill.email> writes:

> Expected output:
> No error fontification of header line: Compilation started at Sun Sep
> 27 11:48:24
>
> Actual output:
> Error fontified line: Compilation started at Sun Sep 27 11:48:24

I can reproduce this in Emacs 28, too, and I'm not sure how to fix it.
You'd think there'd be a way to tell the font-locking mechanism (which I
assume is used here?) to stay away from certain regions of the buffer,
but reading the documentation, I couldn't find anything.

But there surely must be.  Anybody know?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2020-09-28 13:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-27 10:45 bug#43651: 27.1; compile.el should not parse its own header for errors David Landell
     [not found] ` <handler.43651.B.160122468524977.ack@debbugs.gnu.org>
2020-09-27 16:56   ` bug#43651: Acknowledgement (27.1; compile.el should not parse its own header for errors) David Landell
2020-09-28 13:46 ` Lars Ingebrigtsen [this message]
2020-09-28 14:40   ` bug#43651: 27.1; compile.el should not parse its own header for errors David Landell
2020-09-29 14:01     ` Lars Ingebrigtsen

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=87lfguui8b.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=43651@debbugs.gnu.org \
    --cc=david.landell@sunnyhill.email \
    /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.