From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: RE: 23.0.50; face-problems with multy-tty Date: Sun, 23 Sep 2007 17:22:12 -0700 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-15" Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1190593427 15340 80.91.229.12 (24 Sep 2007 00:23:47 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 24 Sep 2007 00:23:47 +0000 (UTC) Cc: emacs-devel@gnu.org To: , =?ISO-8859-15?Q?Johan_=22Bockg=E5rd=22?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Sep 24 02:23:41 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 1IZbjg-0003cL-Du for ged-emacs-devel@m.gmane.org; Mon, 24 Sep 2007 02:23:40 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IZbjd-0005yr-Qv for ged-emacs-devel@m.gmane.org; Sun, 23 Sep 2007 20:23:37 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IZbjU-0005uz-Ar for emacs-devel@gnu.org; Sun, 23 Sep 2007 20:23:28 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IZbjS-0005tX-FW for emacs-devel@gnu.org; Sun, 23 Sep 2007 20:23:27 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IZbjS-0005tI-7u for emacs-devel@gnu.org; Sun, 23 Sep 2007 20:23:26 -0400 Original-Received: from rgminet01.oracle.com ([148.87.113.118]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1IZbjQ-0001BV-Af; Sun, 23 Sep 2007 20:23:24 -0400 Original-Received: from agmgw1.us.oracle.com (agmgw1.us.oracle.com [152.68.180.212]) by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id l8O0NL7s016380; Sun, 23 Sep 2007 18:23:21 -0600 Original-Received: from acsmt350.oracle.com (acsmt350.oracle.com [141.146.40.150]) by agmgw1.us.oracle.com (Switch-3.2.0/Switch-3.2.0) with ESMTP id l8NKSmJW032011; Sun, 23 Sep 2007 18:23:20 -0600 Original-Received: from dhcp-amer-whq-csvpn-gw3-141-144-80-220.vpn.oracle.com by acsmt351.oracle.com with ESMTP id 3238447291190593308; Sun, 23 Sep 2007 17:21:48 -0700 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 X-Brightmail-Tracker: AAAAAQAAAAI= X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Whitelist: TRUE X-Detected-Kernel: Linux 2.4-2.6 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:79636 Archived-At: > (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. > > 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. That way would seem correct (natural) to me. Why should either prevent the effect of the other, if the other comes later? Why would set-face-attribute have higher priority? Are there rules defined for this, or is this the first discussion? I'd say keep it simple: the latest modification wins, however it is made. [I did not follow the whole thread, so ignore if I'm missing something.]