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: highlight failed part of isearch input Date: Sun, 24 Feb 2008 15:47:08 -0800 Message-ID: <003501c8773f$91c6a9a0$0600a8c0@us.oracle.com> References: <008101c86d06$31c2f1f0$9eb22382@us.oracle.com><87fxvzxc0j.fsf@jurta.org><000901c86d0f$5beec1d0$405a908d@us.oracle.com><87lk5r3sf7.fsf@bzg.ath.cx> <87skzsvhvc.fsf@jurta.org><8763wfpi9w.fsf@jurta.org><003001c87662$f62a0280$0600a8c0@us.oracle.com><87fxvjmj7c.fsf@jurta.org><003801c87671$9926fbb0$0600a8c0@us.oracle.com><878x1a8gdc.fsf@jurta.org> <200802242331.m1ONVFeL010174@sallyv1.ics.uci.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1203896946 12211 80.91.229.12 (24 Feb 2008 23:49:06 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 24 Feb 2008 23:49:06 +0000 (UTC) Cc: emacs-devel@gnu.org To: , "'Juri Linkov'" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Feb 25 00:49:31 2008 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 1JTQb1-0001HT-4R for ged-emacs-devel@m.gmane.org; Mon, 25 Feb 2008 00:49:27 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JTQaV-0006zo-DY for ged-emacs-devel@m.gmane.org; Sun, 24 Feb 2008 18:48:55 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JTQaP-0006v5-Oi for emacs-devel@gnu.org; Sun, 24 Feb 2008 18:48:49 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JTQaO-0006ru-4s for emacs-devel@gnu.org; Sun, 24 Feb 2008 18:48:49 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JTQaO-0006rm-1T for emacs-devel@gnu.org; Sun, 24 Feb 2008 18:48:48 -0500 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 1JTQaN-0007dW-Lz for emacs-devel@gnu.org; Sun, 24 Feb 2008 18:48:47 -0500 Original-Received: from agmgw2.us.oracle.com (agmgw2.us.oracle.com [152.68.180.213]) by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id m1ONmg2P003407; Sun, 24 Feb 2008 16:48:42 -0700 Original-Received: from acsmt350.oracle.com (acsmt350.oracle.com [141.146.40.150]) by agmgw2.us.oracle.com (Switch-3.2.0/Switch-3.2.0) with ESMTP id m1ONmgke024320; Sun, 24 Feb 2008 16:48:42 -0700 Original-Received: from inet-141-146-46-1.oracle.com by acsmt351.oracle.com with ESMTP id 3587973471203896832; Sun, 24 Feb 2008 15:47:12 -0800 Original-Received: from dradamslap1 (/141.144.72.115) by bhmail.oracle.com (Oracle Beehive Gateway v4.0) with ESMTP ; Sun, 24 Feb 2008 15:47:12 -0800 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <200802242331.m1ONVFeL010174@sallyv1.ics.uci.edu> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Thread-Index: Ach3PWmxpAZQmJukTfee4Q/yQ25/PQAAC1Qg X-Brightmail-Tracker: AAAAAQAAAAI= X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Whitelist: TRUE X-detected-kernel: by monty-python.gnu.org: 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:90313 Archived-At: > Please no #f!#%@, use a readable color name, there's plenty of them... Why? The user sees the color in Customize (and in isearch). What's the problem with using an unnamed color as the default? FWIW, a name such as "peru" tells me less about a color than its RGB name: #FFFFA7BA4E60. That at least says that there is a max of red, quite a bit of green, and a little blue. Red + green = yellow/brown, so you have some idea what to expect. With the color name "peru" you might expect a ceviche lime green or a Pacific blue or anything else - no help at all. Such hex codes are second nature to those who design and implement with Web pages (which includes a lot of programmers), and even for novices they can say as much or more about a color as an English name. But any name or coding is not that helpful to get an idea of a color - you have to see it. I don't think we should pick colors for UI design (e.g. defaults) based on their names, but based on their properties. Pick the right color, regardless of what convention we use to name it.