all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: <3042@emacsbugs.donarmstrong.com>, <emacs-pretest-bug@gnu.org>
Subject: bug#3042: 23.0.92; display-visual class doc
Date: Sat, 18 Apr 2009 12:32:35 -0700	[thread overview]
Message-ID: <000101c9c05c$6da45420$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <001e01c9bfee$7f5fb470$0200a8c0@us.oracle.com>

> The doc does not explain what the possible values mean. There are no
> other occurrences of the various values (e.g. `static-color') in the
> Elisp manual or other doc strings (that I can find) than what is said
> about `display-visual-class'.
>  
> To use a function, it helps to know its possible values, but if you
> have no idea what those values indicate or mean, then you really don't
> know much about the function.
>  
> Grepping the Emacs sources doesn't really help here either. Looking at
> the definition of `display-visual-class', you can at least learn
> something (partial) about `static-color' and `static-gray', but that's
> about it.

Not being very knowledgeable in this area, I googled a bit. "Color cell" didn't
turn up much. This term needs explaining, no doubt.

Wikipedia helped with this page, which I got to after looking at the bit-plane
page:
http://en.wikipedia.org/wiki/Color_depth. We might draw on its description of
"direct color" and "true color", for example. I'm guessing that what we call
"static color" might be what that page calls "indexed color"? If so, perhaps we
should also mention that term, if it's commonly used.

HTH.







  reply	other threads:[~2009-04-18 19:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-18  6:25 bug#3042: 23.0.92; display-visual class doc Drew Adams
2009-04-18 19:32 ` Drew Adams [this message]
2011-07-11 14:37 ` Lars Magne Ingebrigtsen
2011-07-11 15:41   ` Drew Adams

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='000101c9c05c$6da45420$0200a8c0@us.oracle.com' \
    --to=drew.adams@oracle.com \
    --cc=3042@emacsbugs.donarmstrong.com \
    --cc=emacs-pretest-bug@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 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.