From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Reitter Newsgroups: gmane.emacs.devel Subject: Re: Info about color-values need be revised Date: Wed, 19 Aug 2009 00:22:09 -0400 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (Apple Message framework v1074) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1250655752 7608 80.91.229.12 (19 Aug 2009 04:22:32 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 19 Aug 2009 04:22:32 +0000 (UTC) Cc: 'CHENG Gao' , Drew Adams , emacs-devel@gnu.org To: YAMAMOTO Mitsuharu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Aug 19 06:22:25 2009 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 1Mdcgq-0003kZ-QK for ged-emacs-devel@m.gmane.org; Wed, 19 Aug 2009 06:22:25 +0200 Original-Received: from localhost ([127.0.0.1]:50715 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mdcgq-00047N-4i for ged-emacs-devel@m.gmane.org; Wed, 19 Aug 2009 00:22:24 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mdcgk-000453-FU for emacs-devel@gnu.org; Wed, 19 Aug 2009 00:22:18 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mdcgi-00041y-NI for emacs-devel@gnu.org; Wed, 19 Aug 2009 00:22:17 -0400 Original-Received: from [199.232.76.173] (port=43604 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mdcgi-00041W-HB for emacs-devel@gnu.org; Wed, 19 Aug 2009 00:22:16 -0400 Original-Received: from qw-out-1920.google.com ([74.125.92.146]:15611) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mdcgi-0003XX-AA for emacs-devel@gnu.org; Wed, 19 Aug 2009 00:22:16 -0400 Original-Received: by qw-out-1920.google.com with SMTP id 5so2175736qwf.24 for ; Tue, 18 Aug 2009 21:22:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=fTu8WF+ynNGfcLvtGq8fXGMAbRbUy7L2OY/SseecIZI=; b=O/0hgzljlmJ+2zPlJUWjZBkBxHMDzakjDEpEF5ZegQUaz9g7DSsBa8A+SvqcVyGgyt SumHfbRsfbZNRG8qqLo1CXUTSYNP85WRlBkjZCRxWbA9JEbeZQP6HNmkkKBAaOYH5KA7 K0Mjr76WA4xa4+DrgpMdS9mJSGVwGOvs1ohJQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=M1/4YSznUMlJ2wBICj5bsLMf9qrdbjRAeHnYB9crD7gaeAOoQkIaV3ARwu1PV9zNSt QnWlCbuJXuLkcvUSYCeDHbYSPSgpFjMJw2T6pxBCkBiYXdQTPTlZyKkpRj695USZLJ3V KmRNdpyrz9XDlcfrUHb7BI2vBDf9TCvZz8PfY= Original-Received: by 10.224.7.16 with SMTP id b16mr6078572qab.94.1250655734533; Tue, 18 Aug 2009 21:22:14 -0700 (PDT) Original-Received: from scarlett.local (pool-72-95-249-90.pitbpa.east.verizon.net [72.95.249.90]) by mx.google.com with ESMTPS id 8sm11763408qwj.36.2009.08.18.21.22.11 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 18 Aug 2009 21:22:12 -0700 (PDT) In-Reply-To: X-Mailer: Apple Mail (2.1074) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) 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:114394 Archived-At: On Aug 18, 2009, at 11:47 PM, YAMAMOTO Mitsuharu wrote: > As I've been saying, the alpha component support in the NS port should > have been removed in the first place. > > Does anyone oppose doing that (again) in the trunk? > > Also, we can observe that users tend to spread (*) such an eye candy > feature without caring about various compatibility issues or the GNU > policy. That's why it was important to get rid of such a feature from > the release version. You were right about these things for the release, but as for the trunk, could people please consider the alternative: Adding transparency to the other platforms where the APIs support it easily, and creating Lisp-level compatibility for transparency in the color specification. -? It is no surprise that folks roll their own if the mothership is so far behind the times with such features. And people do it on those platforms first where it is easy because the right OS layer provides APIs for it; especially if the platform is so popular. And once people like me add their own features, they get used, and the Lisp APIs diverge. What has the purposeful GNU policy achieved then? ps: Nota bene: You personally are not the tree up which I am barking when it comes to lack of implementation activity...