From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: bojohan+news@dd.chalmers.se (Johan =?utf-8?Q?Bockg=C3=A5rd?=) Newsgroups: gmane.emacs.devel Subject: Re: 23.0.50; face-problems with multy-tty Date: Mon, 24 Sep 2007 02:00:21 +0200 Message-ID: References: <87ejhcmgp2.fsf@baldur.tsdh.de> <200709062116.l86LGWnO000262@oogie-boogie.ics.uci.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: sea.gmane.org 1190592073 12417 80.91.229.12 (24 Sep 2007 00:01:13 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 24 Sep 2007 00:01:13 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Sep 24 02:01:07 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1IZbNr-0007w9-AQ for ged-emacs-devel@m.gmane.org; Mon, 24 Sep 2007 02:01:07 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IZbNo-0001k9-GQ for ged-emacs-devel@m.gmane.org; Sun, 23 Sep 2007 20:01:04 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IZbNl-0001jr-QI for emacs-devel@gnu.org; Sun, 23 Sep 2007 20:01:02 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IZbNl-0001iR-2B for emacs-devel@gnu.org; Sun, 23 Sep 2007 20:01:01 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IZbNk-0001iI-KA for emacs-devel@gnu.org; Sun, 23 Sep 2007 20:01:00 -0400 Original-Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1IZbNk-0006ET-0w for emacs-devel@gnu.org; Sun, 23 Sep 2007 20:01:00 -0400 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1IZbNT-0008P0-FB for emacs-devel@gnu.org; Mon, 24 Sep 2007 00:00:43 +0000 Original-Received: from gamma02.me.chalmers.se ([129.16.50.72]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 24 Sep 2007 00:00:43 +0000 Original-Received: from bojohan+news by gamma02.me.chalmers.se with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 24 Sep 2007 00:00:43 +0000 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 51 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: gamma02.me.chalmers.se Mail-Copies-To: never User-Agent: Gnus/5.110007 (No Gnus v0.7) Emacs/22.1.50 (gnu/linux) Cancel-Lock: sha1:uK6AeXbjQghaNGPpIc6jTeLJET4= X-Detected-Kernel: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:79630 Archived-At: Richard Stallman writes: > (set-face-attribute 'font-lock-string-face nil :foreground "yellow") > > (custom-set-faces > '(font-lock-string-face > ((((class color) (background light)) (:foreground "red")) > (((class color) (background dark)) (:foreground "blue"))))) > > ;; `C-x 5 2' uses a yellow font-lock-string-face. > > I am not convinced that is a bug. > > The new-frame default face attributes override customizations because > they are usually set by programs during a session, whereas > customizations are usually set semipermanently. In that kind of case, > it is right for the default face attributes to take precedence. I'm not convinced. The behavior that "new-frame default face attributes override customizations" is only two weeks old. It didn't use to work like that (see below). > Customizations can also be made within a session. In that case, it is > not clear which should take precedence. > > Thus, the current precedence order seems better, overall, than the > opposite order. > > As long as we stick with this order, we should do it consistently. > So the init file you showed should produce the results it produces. > If you don't like it, don't do that. It wasn't an example of a real init file. The case I'm worried about is when you want to reset the faces from the init file with `C-x C-e' on the custom-set-faces form (or by loading the file). > Another consistent possibility is that the new-frame default face > attributes and face customizations have the same precedence. But the > only consistent way to do that is if each one erases the other, so you > can only have one of them. So if you customize the face, that clears > out all new-frame default face attributes, and if you set a new-frame > default face attribute, that clears the customization. Note that this is how it already worked before the recent changes. custom-set-faces used to operate by changing the new-frame defaults. The problem is that that doesn't distinguish between different kinds of frames. Now custom-set-faces sets the attributes per frame (via face-spec-set), but it needs to clear the new-frame defaults too. -- Johan Bockgård