From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dan Nicolaescu Newsgroups: gmane.emacs.devel Subject: Re: font-lock-comment-delimiter-face Date: Thu, 19 May 2005 09:52:54 -0700 Message-ID: <200505191652.j4JGqsHc011903@amrm2.ics.uci.edu> References: <87wtq3ydmf.fsf-monnier+emacs@gnu.org> <17029.21411.495779.643570@farnswood.snap.net.nz> <17030.32533.416687.524645@farnswood.snap.net.nz> <85k6m04y6f.fsf@lola.goethe.zz> <857ji0nly2.fsf@lola.goethe.zz> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1116523453 29208 80.91.229.2 (19 May 2005 17:24:13 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 19 May 2005 17:24:13 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu May 19 19:24:11 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DYoiR-0005lP-68 for ged-emacs-devel@m.gmane.org; Thu, 19 May 2005 19:21:47 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DYol7-0001Fk-0N for ged-emacs-devel@m.gmane.org; Thu, 19 May 2005 13:24:33 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DYokx-0001Er-JN for emacs-devel@gnu.org; Thu, 19 May 2005 13:24:23 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DYogv-0000Vz-4w for emacs-devel@gnu.org; Thu, 19 May 2005 13:20:13 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DYogu-0000Px-0v for emacs-devel@gnu.org; Thu, 19 May 2005 13:20:12 -0400 Original-Received: from [128.195.11.178] (helo=localhost.localdomain) by monty-python.gnu.org with esmtp (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.34) id 1DYoOm-0006t1-Vk; Thu, 19 May 2005 13:01:29 -0400 Original-Received: from amrm2.ics.uci.edu (amrm2.ics.uci.edu [127.0.0.1]) by localhost.localdomain (8.13.1/8.13.1) with ESMTP id j4JGqs6c011904; Thu, 19 May 2005 09:52:54 -0700 Original-Received: (from dann@localhost) by amrm2.ics.uci.edu (8.13.1/8.13.1/Submit) id j4JGqsHc011903; Thu, 19 May 2005 09:52:54 -0700 Original-To: rms@gnu.org In-Reply-To: (Richard Stallman's message of "Wed, 18 May 2005 18:44:27 -0400") Original-Lines: 33 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:37361 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:37361 Richard Stallman writes: > I don't mean to sound hostile, but I don't see what is wrong with a > simple user customization. I don't understand why you would make large > changes to Emacs when you could simply change the offending face on your > machine. > > I don't think I am the only user who uses a console and finds > comments in red hard to read. Nor the only one who would like comment > delimiters in red. And this is a small change. If the red colored comments are hard to read on a console, can't we just change the face foreground for font-lock-comment-face for that situation (i.e. min-colors == 8 and background-mode == 'dark)? It seems to me that would be a lot easier than adding font-lock-comment-delimiter-face route? We could either swap the color used by font-lock-comment-face with one of the other font-lock faces, or use the same color for both font-lock-comment-face and another face. it's not like there's a lot of choice for colors (only 8), or very likely to confuse comments with anything else. So just do M-x list-colors-display RET pick a color for comments and I'll do the needed change. PS: Offtopic wish: I would be nice if the Linux console allowed for more than 8 colors to be used (like 256 colors). Maybe this is not even hard to do, now that a lot of machines use a frame buffer console. Any linux guys listening? (No, I have no idea if this is possible or desirable)