Invalid face reference: nil [296 times]

Invalid face reference: nil [296 times]

[zhang cc]

I see some error message in the *Message* buffer like this:

Invalid face reference: nil [296 times]


I don’t known when it was printed. I didn’t see it in minibuffer.
Maybe there is a invalid face? Can the face name be printed?
How to debug this?

Re: Invalid face reference: nil [296 times]

[Emanuel Berg]

zhang cc wrote:

> I don’t known when it was printed. I didn’t
> see it in minibuffer. Maybe there is
> a invalid face? Can the face name be printed?
> How to debug this?

Check your init files for all references to
"face", then look for anything in particular
that looks suspicious...

-- 
underground experts united
http://user.it.uu.se/~embe8573

Re: Invalid face reference: nil [296 times]

[Michael Heerdegen]

Emanuel Berg <moasen@zoho.com> writes:

> > I don’t known when it was printed. I didn’t see it in
> > minibuffer. Maybe there is a invalid face? Can the face name be
> > printed?  How to debug this?
>
> Check your init files for all references to "face", then look for
> anything in particular that looks suspicious...

You can also try to find out if these messages only appear when windows
whose buffers are in a certain mode are selected, so that you have a
hint where the problem could come from.

Besides that, AFAICT there is no straightforward way to debug this with
a debugger or so.  Bisecting your init file always works of course but
is not very effective.


Michael.

Re: Invalid face reference: nil [296 times]

[Emanuel Berg]

Michael Heerdegen wrote:

> Besides that, AFAICT there is no
> straightforward way to debug this with
> a debugger or so. Bisecting your init file
> always works of course but is not
> very effective.

If you care about efficiency, probably should
throw those init files away, right? :)

No, but it can be made more efficient if they
are organized. For example, one can have one
file called my-faces.el and all face stuff goes
into there. So when there is a face related
problem, in the main init file just comment-out
that line which loads the face file.

-- 
underground experts united
http://user.it.uu.se/~embe8573

Re: Invalid face reference: nil [296 times]

[andlind]

On Friday, 9 March 2018 16:25:19 UTC+1, zhang cc  wrote:
> I see some error message in the *Message* buffer like this:
> 
> Invalid face reference: nil [296 times]
> 
> 
> I don’t known when it was printed. I didn’t see it in minibuffer.
> Maybe there is a invalid face? Can the face name be printed?
> How to debug this?

Does it disappear if you turn font-lock globally off?

If so, turn it back on in buffer after buffer util it appears again.

Once you have found a buffer that triggers the problem, you can inspect the font-lock rules to see if you find a bad face reference.

One way of doing this is to single-step the font-lock rules using `font-lock-studio' (available from Melpa).

If font-lock isn't causing this, check if you have a custom setup for the mode line, or anything else face-related in your init file.

    -- Anders