unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: face colors on 256 colors terminals
Date: Thu, 07 Apr 2005 06:53:28 +0300	[thread overview]
Message-ID: <01c53b25$Blat.v2.4$80e8db20@zahav.net.il> (raw)
In-Reply-To: <200504062134.j36LY8AH022227@scanner2.ics.uci.edu> (message from Dan Nicolaescu on Wed, 06 Apr 2005 14:34:06 -0700)

> Cc: emacs-devel@gnu.org
> From: Dan Nicolaescu <dann@ics.uci.edu>
> Date: Wed, 06 Apr 2005 14:34:06 -0700
> 
> "Eli Zaretskii" <eliz@gnu.org> writes:
> 
>   > > From: Dan Nicolaescu <dann@ics.uci.edu>
>   > > Some standard face definitions use colors like "red" or "blue". They 
>   > > should be changed "red1" (or "blue1")
>   > 
>   > Yes, I agree.  Can you post a patch to do that?
> 
> Here it is. It replaces: 
> 	red->red1
> 	green->green1
> 	blue->blue1
> 	yellow->yellow1
> 	cyan->cyan1
> 	magenta->magenta1
> 
> The replacements were done so that not change anything for faces that
> had a special treatment for ttys, pc, etc. 

Thanks.

> Is this OK? 
> 
> Index: lisp/comint.el
> ===================================================================
> RCS file: /cvsroot/emacs/emacs/lisp/comint.el,v
> retrieving revision 1.310
> diff -c -3 -p -r1.310 comint.el
> *** lisp/comint.el	5 Apr 2005 01:21:23 -0000	1.310
> --- lisp/comint.el	6 Apr 2005 21:24:52 -0000
> *************** This variable is buffer-local."
> *** 228,234 ****
>     :group 'comint)
>   
>   (defface comint-highlight-prompt
> !   '((((background dark)) (:foreground "cyan"))
>       (t (:foreground "dark blue")))
>     "Face to use to highlight prompts."
>     :group 'comint)
> --- 228,234 ----
>     :group 'comint)
>   
>   (defface comint-highlight-prompt
> !   '((((background dark)) (:foreground "cyan1"))
>       (t (:foreground "dark blue")))
>     "Face to use to highlight prompts."
>     :group 'comint)

Hmmm... "bother", as they say.  The changes to the face colors that
are under (min-colors 88) or when there's a separate color for less
color-capable displays are okay.  But there are few cases where
there's a single color definition, like the one above, which is
applicable to all color-capable displays.  In these cases, the changes
you suggest will have a significant effect on 16-color text terminals,
because cyan1, blue1, red1 etc. are translated to the bright shades of
the respective colors, so what was red will now be brightred.  The
bright shades are quite annoying in many situations.

So I think we should change this patch so as not to change the color
definitions on displays that support less than 88 colors.  That is, in
those cases where there's a single color definition, split it into 2
and change only the one for >88 colors.

  parent reply	other threads:[~2005-04-07  3:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-06  8:17 face colors on 256 colors terminals Dan Nicolaescu
2005-04-06 17:23 ` Eli Zaretskii
2005-04-06 17:36   ` David Kastrup
2005-04-06 17:46     ` Eli Zaretskii
2005-04-06 18:03       ` David Kastrup
2005-04-06 18:26     ` Dan Nicolaescu
2005-04-07 20:43     ` James Cloos
2005-04-08  1:17       ` Dan Nicolaescu
2005-04-08 10:52         ` Eli Zaretskii
2005-04-08 15:13           ` Dan Nicolaescu
2005-04-09  8:06             ` Eli Zaretskii
2005-04-06 17:52   ` Dan Nicolaescu
     [not found]     ` <01c53aea$Blat.v2.4$16ee4740@zahav.net.il>
2005-04-06 23:50       ` Dan Nicolaescu
2005-04-07  0:22         ` David Kastrup
2005-04-07  3:58           ` Eli Zaretskii
2005-04-07  5:14           ` Dan Nicolaescu
2005-04-07 10:23             ` David Kastrup
2005-04-08  1:13               ` Dan Nicolaescu
2005-04-07  3:55         ` Eli Zaretskii
     [not found]   ` <200504062134.j36LY8AH022227@scanner2.ics.uci.edu>
2005-04-07  3:53     ` Eli Zaretskii [this message]
2005-04-07 18:27       ` Dan Nicolaescu
2005-04-08 10:54         ` Eli Zaretskii

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='01c53b25$Blat.v2.4$80e8db20@zahav.net.il' \
    --to=eliz@gnu.org \
    --cc=emacs-devel@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).