From: David De La Harpe Golden <david@harpegolden.net>
To: Emacs developers <emacs-devel@gnu.org>
Cc: Yavuz <justloop@gmail.com>
Subject: Re: customize-themes doesn't allow backquote or :inherit
Date: Mon, 18 Oct 2010 21:30:18 +0100 [thread overview]
Message-ID: <4CBCAE5A.5020104@harpegolden.net> (raw)
In-Reply-To: <loom.20101018T184615-559@post.gmane.org>
On 18/10/10 18:54, Yavuz wrote:
> Thinking a bit laterally, there are 2 alternate mechanisms that
> could help (at the loss of some flexibility):
>
> 1. There are named colors, such as "royal blue" that one can use
> instead of "#RRGGBB" format. If it were possible to user-define
> more, that would be a solution.
This is possible on X11, but not in the manner you mean: Those named
colors are actually provided by the system.
Emacs bundles a copy of a historic de-facto standard set of named colors
for non-x11 use. The set of named colors adopted by modern web browsers
was also largely based on that set, with some small changes [1].
However on real X11 (at least x.org and friends), the set of named
colors is user-extensible e.g. if you place the following in ~/.xcms.txt
XCMS_COLORDB_START 0.1
Blobby RGB:7fe2/ffe1/331a
XCMS_COLORDB_END
and then
export XCMSDB=~/.xcms.txt
and run emacs in that environment, you'll have the color "blobby"
available in emacs (and any other x11 app which uses the relevant x11
color api).
None of that means emacs couldn't support internal user-defined named
colors, or any number of other things [2], just pointing out where they
currently come from.
[1] http://en.wikipedia.org/wiki/X11_color_names
[2] e.g. I suggested - not too seriously - note the "may be
overcomplicating things" - an ability to indirect through alists when
resolving colors last time the matter came up:
http://lists.gnu.org/archive/html/emacs-devel/2009-08/msg00124.html
prev parent reply other threads:[~2010-10-18 20:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-17 18:47 customize-themes doesn't allow backquote or :inherit Yavuz
2010-10-17 21:20 ` Chong Yidong
2010-10-17 21:30 ` Miles Bader
2010-10-18 13:52 ` Stefan Monnier
2010-10-18 16:26 ` Chong Yidong
2010-10-18 17:54 ` Yavuz
2010-10-18 20:30 ` David De La Harpe Golden [this message]
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=4CBCAE5A.5020104@harpegolden.net \
--to=david@harpegolden.net \
--cc=emacs-devel@gnu.org \
--cc=justloop@gmail.com \
/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).