From: Nick Roberts <nickrob@snap.net.nz>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: Rob Riepel <riepel@networking.stanford.edu>,
emacs-pretest-bug@gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: Re: incomplete comment colorization in terminals
Date: Wed, 12 Mar 2008 21:17:00 +1300 [thread overview]
Message-ID: <18391.37244.140676.65895@kahikatea.snap.net.nz> (raw)
In-Reply-To: <200803120644.m2C6i8fa000584@sallyv1.ics.uci.edu>
> > This is not a bug, but a deliberate feature. There's a new face named
> > font-lock-comment-delimiter-face.
>
> This feature was introduced because on the Linux console the comment
> face was hard to read (red on black).
That's not my recollection. Indeed red is very easy to see on black when
there is sufficient brightness. ISTR that RMS added it to minimise power
consumption on laptops.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2008-03-12 8:17 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18391.37244.140676.65895@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=dann@ics.uci.edu \
--cc=eliz@gnu.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=riepel@networking.stanford.edu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.