Re: Find out what is setting color in minibufer

[Alex Kost]

Alex Kost (2016-11-26 22:02 +0300) wrote:

> Fernando Basso (2016-11-25 20:45 -0200) wrote:
>
>> I have been using Emacs from the terminal recently. It works fine and it
>> helps me with my tmux workflow. However, when I am using Geiser mode the
>> minibuffer shows documentation hints in a shade of blue that makes it hard
>> to read. I don't know if it is Geiser or something else that is setting
>> that color. It seems the color remains even if I load a different theme.
>> Also, that color is not set in my Xresources file.
>>
>> How should I proceed to find out what is setting that color? Emacs 25 on
>> arch linux.
>>
>> I am attaching a screenshot in the hope that it will help.
>
> This is 'geiser-font-lock-autodoc-identifier' face which should have the
> same look as 'font-lock-function-name-face' by default.  So it's either
> your custom theme or your customization that you should blame.

Sorry, I think I was wrong.  It's likely not the fault of your theme.
The problem is that this face *does not inherit* from
'font-lock-function-name-face' but it uses its default specification
instead:

  (defface geiser-font-lock-autodoc-identifier
    (face-default-spec 'font-lock-function-name-face)
    "Face for highlighting procedure name in autodoc messages."
    :group 'geiser-autodoc
    :group 'geiser-faces)

(this is actually done via 'geiser-custom--defface' macro but it doesn't
matter:
<https://github.com/jaor/geiser/blob/master/elisp/geiser-autodoc.el#L32-L34>)

So if your theme changes 'font-lock-function-name-face', that autodoc
face will still use the default face specification (which apparently
doesn't look good in a terminal).

After all, I would say it's a Geiser problem: faces should inherit from
other (particuarly 'font-lock') faces and should not copy their specs as
it is done in Geiser faces.

-- 
Alex