unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-pretest-bug@gnu.org, emacs-devel@gnu.org
Subject: Re: Mode-line face bug
Date: Sat, 10 Mar 2007 10:51:21 -0500	[thread overview]
Message-ID: <E1HQ3qr-0004yh-00@fencepost.gnu.org> (raw)
In-Reply-To: <87fy8ez8pr.fsf@stupidchicken.com> (message from Chong Yidong on Fri, 09 Mar 2007 11:24:00 -0500)

    Another possibility is to stop the window manager from automatically
    setting a face resource for the mode-line.  There would then be no
    problem with the convention that X resources override Elisp, since X
    resources would be set by the user.

That is an interesting way of looking at it.  I have asked the GNOME
developers to turn off the setting for mode-line, for other reasons.
However, the theme manager also makes settings for other faces, such as
scroll-bar, so the problem would still exist.

It could be that the theme-based settings for other faces won't bother
many users, so few will try to override them by customization.
If so, the remaining problem would not bother people very much.
It would still be a problem, but less urgent.

However, that's academic, because even if the GNOME developers listen
to us, it will take a long time for corrected versions of GNOME to
replace the current ones.  So we need a fix for this now, even if we
won't need it badly 3 years from now.

Here is an idea.  When a face attribute is set by customization,
set a flag to record that fact.  That flag will cause the X resource
to be ignored for that attribute.

Do you agree that is feasible?  Can you implement it?

  parent reply	other threads:[~2007-03-10 15:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m2wt1uejho.fsf@sl392.st-edmunds.cam.ac.uk>
     [not found] ` <E1HOiHV-00011g-QI@fencepost.gnu.org>
     [not found]   ` <m2irdddhja.fsf@sl392.st-edmunds.cam.ac.uk>
     [not found]     ` <E1HOsAp-0004Gt-PD@fencepost.gnu.org>
     [not found]       ` <m2wt1tbefj.fsf@sl392.st-edmunds.cam.ac.uk>
2007-03-08  3:15         ` Mode-line face bug Richard Stallman
2007-03-09 16:24           ` Chong Yidong
2007-03-09 23:03             ` Kim F. Storm
2007-03-11  4:23               ` Richard Stallman
2007-03-11 18:58                 ` Kim F. Storm
2007-03-10 15:51             ` Richard Stallman [this message]
2007-03-10 17:57               ` Chong Yidong
2007-03-11 15:08                 ` Chong Yidong
2007-03-11 15:55                   ` Leo
2007-03-11 17:28                     ` Chong Yidong
2007-03-12  1:27                   ` Richard Stallman
2007-03-12  3:08                     ` Glenn Morris
2007-03-11 20:00                 ` Richard Stallman

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=E1HQ3qr-0004yh-00@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-pretest-bug@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).