unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: lennart.borgman.073@student.lu.se, emacs-devel@gnu.org
Subject: Re: Faces for Mode Line and Mode Line Inactive
Date: Sun, 05 Dec 2004 20:40:41 -0500	[thread overview]
Message-ID: <E1Cb7rl-00019x-BE@fencepost.gnu.org> (raw)
In-Reply-To: <01c4db0f$Blat.v2.2.2$1ee17160@zahav.net.il> (eliz@gnu.org)

    ??? Look at faces.el, around line 1780, where these two faces are
    defined: mode-line-inactive inherits from mode-line only for terminals
    that don't support colors and/or :style attributes.  Otherwise,
    mode-line defines different colors and a released-button style.

I tried this under X, and found that it was as Lennart said:
mode-line-inactive inherits from mode-line and specifies no changes.

So I tried changing the defface of mode-line-inactive, putting
the t clause to the end.  Then customize-face showed the proper
values.

Maybe customize-face is not handling the choice of clause the same way
that defface does.  face-spec-choose seems to put the t attributes at
the end after the more specific attributes.  The result is that the t
attributes don't entirely override everything if they come first.

I get the impression that face-spec-choose is trying to avoid dependence
on the order of the alternatives, but not entirely succeeding.

For customize-face, it looks like the function that handles this is
custom-filter-face-spec.  I don't understand it, but I suspect it
disagrees with what face-spec-choose does.

  parent reply	other threads:[~2004-12-06  1:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-05  0:06 Faces for Mode Line and Mode Line Inactive Lennart Borgman
2004-12-05 21:11 ` Eli Zaretskii
2004-12-05 22:43   ` Lennart Borgman
2004-12-05 23:14     ` Stefan Monnier
2004-12-06 18:47       ` Dan Nicolaescu
2004-12-06  1:40   ` Richard Stallman [this message]
2004-12-05 22:45 ` John Paul Wallington
2004-12-05 23:17   ` Stefan Monnier

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=E1Cb7rl-00019x-BE@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lennart.borgman.073@student.lu.se \
    /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).