unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
Cc: Andreas Schwab <schwab@suse.de>, emacs-devel@gnu.org
Subject: Re: supporting more faces on 256 colors xterms
Date: Sun, 08 Feb 2004 15:52:36 -0800	[thread overview]
Message-ID: <200402082352.i18NqY6M003350@gremlin.ics.uci.edu> (raw)
In-Reply-To: <9003-Sun08Feb2004202425+0200-eliz@elta.co.il>

"Eli Zaretskii" <eliz@elta.co.il> writes:

  > > From: Andreas Schwab <schwab@suse.de>
  > > Date: Sun, 08 Feb 2004 14:45:28 +0100
  > > 
  > > How about min-colors?
  > 
  > Okay, but what to do with the opposite clause, `ncolors<='?  That
  > would be handy for color-challenged devices.

We don't really need both `ncolors>=' and `ncolors<=', `ncolors>=' (or
whatever we decide to call it) is enough. 

Ordering the `ncolors>=' clauses in decreasing order should be enough.
Example:

(defface foo-face
  '((((class color)(ncolors>= 88)) (:foreground "Firebrick"))
    (((class color)(ncolors>= 16)) (:foreground "red"))
    (t (:weight bold :slant italic)))
  "Foo."
  :group 'foo)


The screenshot at http://www.ics.uci.edu/~dann/emacs.jpg
shows of 2 emacs sessions:
emacs -nw -q --no-site-file
emacs  -q --no-site-file&
that show the font-lock faces changed to use the ncolors>= attribute.

As for the name. I would vote for `min-colors'. 

  parent reply	other threads:[~2004-02-08 23:52 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-08  4:13 supporting more faces on 256 colors xterms Dan Nicolaescu
2004-02-08  6:08 ` Eli Zaretskii
2004-02-08  8:15   ` Dan Nicolaescu
2004-02-08 13:45     ` Andreas Schwab
2004-02-08 18:24       ` Eli Zaretskii
2004-02-08 19:11         ` Andreas Schwab
2004-02-08 23:19           ` Miles Bader
2004-02-08 23:52         ` Dan Nicolaescu [this message]
2004-02-09  6:03           ` Eli Zaretskii
2004-02-12 22:13             ` Dan Nicolaescu
2004-02-13  8:57               ` Eli Zaretskii
2004-02-13 20:29                 ` Dan Nicolaescu
2004-02-14 12:15                   ` Eli Zaretskii
2004-02-17 20:30                     ` Dan Nicolaescu
2004-02-13  9:02               ` Eli Zaretskii
2004-06-04 19:42               ` Juri Linkov
2004-06-04 21:14                 ` Dan Nicolaescu
2004-06-04 23:12                   ` Juri Linkov
2004-06-05 22:50                 ` Richard Stallman
2004-02-08 18:35     ` Eli Zaretskii
2004-02-09  9:38 ` Richard Stallman
2004-02-12 18:40   ` small grep.el fix Dan Nicolaescu
2004-02-15 13:13     ` Thien-Thi Nguyen

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=200402082352.i18NqY6M003350@gremlin.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    --cc=schwab@suse.de \
    /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).