unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel <emacs-devel@gnu.org>
Subject: compilation-mode, face, font-lock-face
Date: Thu, 02 Feb 2017 04:52:20 -0600	[thread overview]
Message-ID: <86bmuk27bv.fsf@stephe-leake.org> (raw)

I have an external program that produces messages similar to compilation
errors; they have file name and line numbers.

However, the program is designed to start once, then accept commands on
stdin.

So I can't use 'compilation-start' to send a new command to the program,
but I'd like to use the compilation machinery to highlight the file/line
and navigate to them.

So I start the process, and in the associated buffer I call
compilation-mode, and set compilation-error-regexp-alist.

The file/line locations are recognized, and next-error jumps to them.

However, the buffer is not highlighted.

describe-text-properties shows that there is a font-lock-face property
set appropriately, but the text shows as plain black.

Comparing to a compilation buffer created via M-x compile, I can't
figure out what is different.

As I understand it, 'font-lock-face' is supposed to be set only by
font-lock; 'face' should be set by any other mechanism. So I don't
understand why compile.el is setting 'font-lock-face' instead of 'face'.

Apparently M-x compile does something to font-lock that I'm not doing.

Can anyone explain what's going on?

-- 
-- Stephe



             reply	other threads:[~2017-02-02 10:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-02 10:52 Stephen Leake [this message]
2017-02-02 11:52 ` compilation-mode, face, font-lock-face Michael Heerdegen
2017-02-02 16:47   ` Stephen Leake
2017-02-02 17:33     ` Drew Adams
2017-02-02 19:31       ` Davis Herring
2017-02-02 20:43         ` Anders Lindgren

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=86bmuk27bv.fsf@stephe-leake.org \
    --to=stephen_leake@stephe-leake.org \
    --cc=emacs-devel@gnu.org \
    /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).