unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: David Reitter <david.reitter@gmail.com>
To: Kenichi Handa <handa@m17n.org>
Cc: 3408@emacsbugs.donarmstrong.com
Subject: bug#3408: customize-face not working: seems to apply to frame-face
Date: Wed, 27 May 2009 23:08:45 -0400	[thread overview]
Message-ID: <9A46C94D-EA2B-4721-9B22-4109C6E5085D@gmail.com> (raw)
In-Reply-To: <E1M9V70-0008PF-5R@etlken>

[-- Attachment #1: Type: text/plain, Size: 871 bytes --]

On May 27, 2009, at 10:12 PM, Kenichi Handa wrote:
> If the arg FRAME is nil, set-face-attribute changes
> attributes on all frames plus the default for new frames
>
> But customize-face changes only the attributes of existing
> frames.

> (customize-face 'default) ;; set :background back to "#ffffff"
>
> (face-attribute 'default :background nil) => "#ffffff"
> (face-attribute 'default :background t) => "gray"

So is this a new, intentional "feature"?

I presume there has been a discussion about this... because without  
knowing the reasoning behind this, I'd say it was a bad call.  Very  
confusing to users, who, by default, shouldn't be concerned with frame- 
specific faces.  Note that even "save for future sessions" won't set  
the face for future frames.  How would I set a face through the  
customize interface that is valid for current and future frames?

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2193 bytes --]

  reply	other threads:[~2009-05-28  3:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AD8B1B64-DA4C-4FB1-8B1A-4A4E4FDD503C@gmail.com>
2009-05-28  0:40 ` bug#3408: customize-face not working: seems to apply to frame-face David Reitter
2009-05-28  1:12   ` Glenn Morris
2009-05-28  2:12   ` Kenichi Handa
2009-05-28  3:08     ` David Reitter [this message]
2009-05-28 15:40       ` Drew Adams
2009-05-28  4:53 Chong Yidong
2009-05-28 15:40 ` Drew Adams
2009-05-28 17:08   ` Chong Yidong

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=9A46C94D-EA2B-4721-9B22-4109C6E5085D@gmail.com \
    --to=david.reitter@gmail.com \
    --cc=3408@emacsbugs.donarmstrong.com \
    --cc=handa@m17n.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).