unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: rms@gnu.org
Cc: riepel@networking.stanford.edu, emacs-pretest-bug@gnu.org,
	Nick Roberts <nickrob@snap.net.nz>,
	eliz@gnu.org
Subject: Re: incomplete comment colorization in terminals
Date: Wed, 12 Mar 2008 23:38:17 -0700	[thread overview]
Message-ID: <200803130638.m2D6cILZ010032@sallyv1.ics.uci.edu> (raw)
In-Reply-To: <E1JZV6r-00077U-PX@fencepost.gnu.org> (Richard Stallman's message of "Wed, 12 Mar 2008 13:51:25 -0400")

Richard Stallman <rms@gnu.org> writes:

  > In any case, I would not mind if some other change is made for the
  > white background case.

Thanks. I have done that.

We can actually completely get rid of `font-lock-comment-delimiter-face'
if the color for the dark background, 8 colors is changed to "yellow".
"yellow" is very readable on a black background. It will appear as
orange on the Linux console, which is also very readable.

Of the font-lock faces only font-lock-variable-name-face uses
"yellow". The 2 faces tend to appear in different contexts, so there
should not be a big problem in using the same color for both.

What do you think?





  reply	other threads:[~2008-03-13  6:38 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-11 23:15 incomplete comment colorization in terminals Rob Riepel
2008-03-12  4:26 ` Eli Zaretskii
2008-03-12  6:44   ` Dan Nicolaescu
2008-03-12  8:17     ` Nick Roberts
2008-03-12 13:54       ` Stefan Monnier
2008-03-12 15:07         ` Dan Nicolaescu
2008-03-12 17:51       ` Richard Stallman
2008-03-13  6:38         ` Dan Nicolaescu [this message]
2008-03-13 22:24           ` Richard Stallman
2008-03-13 22:44             ` Dan Nicolaescu
2008-03-14  0:21               ` Nick Roberts
2008-03-14  0:34                 ` Dan Nicolaescu
2008-03-15  4:46                   ` Nick Roberts
2008-03-15  8:34                     ` Dan Nicolaescu
2008-03-15  0:49   ` Rob Riepel
2008-03-15 14:34     ` Eli Zaretskii
2008-03-12  4:45 ` Dan Nicolaescu
2008-03-12 13:57   ` Stefan Monnier
2008-03-13  6:40     ` Dan Nicolaescu
2008-03-13 15:01       ` Stefan Monnier
2008-03-13 18:55         ` Glenn Morris
2008-03-13 21:52           ` Dan Nicolaescu
2008-03-14  4:16           ` Dan Nicolaescu
2008-03-14 15:08             ` Stefan Monnier
2008-03-19  4:02         ` Dan Nicolaescu
2008-03-15  0:50     ` Rob Riepel
2008-03-12 13:10 ` Stefan Monnier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200803130638.m2D6cILZ010032@sallyv1.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=nickrob@snap.net.nz \
    --cc=riepel@networking.stanford.edu \
    --cc=rms@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).