From: Miles Bader <miles@gnu.org>
Cc: Juri Linkov <juri@jurta.org>,
emacs-devel@gnu.org, Miles Bader <miles@gnu.org>
Subject: Re: Buffer-local faces
Date: Tue, 4 May 2004 10:02:41 -0400 [thread overview]
Message-ID: <20040504140241.GB23709@fencepost> (raw)
In-Reply-To: <m14qqw1fqd.fsf-monnier+emacs@gnu.org>
On Tue, May 04, 2004 at 09:37:52AM -0400, Stefan Monnier wrote:
> > It's a much less obvious operation (what does subtracting red from black
> > yield? [Ok, maybe cyan :-]) and I can't offhand think of any obvious uses
> > for it....
>
> As I suggested, we might want to add a notion of color composition, so we
> could have a face that make the foreground darker, or redder, or ...
Yeah, that's one of the areas I've wanted to work on -- I was thinking about
things like `darker'/`lighter'/ `more-intense'/`less-intense' color operators
(the latter two automatically choosing darker or lighter depending on the
context), plus `shaded' versions of the same operators (e.g., doing the
operation with a particular tint).
The reason is so that many faces could be written to be independent of
particular background colors; currently many faces only work well in a single
context (as evidenced by the occasional bickering over face colors :-) --
with such operators, they could even work well in dynamic contexts thanks to
face merging.
I don't know about CMY vs. RGB though -- in my somewhat limited experience,
_all_ color systems suck for this of thing... :-)
> I'm not sure what's a useful generalization, maybe a "filtered inheritance"
> where you can specify which attributes are inherited from a given parent.
Yeah, the question is what's a good way to specify it? It's always tempting
to just throw in lisp code, but we've seen the messes that gets us into with
the signal handlers &c...
-Miles
--
`There are more things in heaven and earth, Horatio,
Than are dreamt of in your philosophy.'
next prev parent reply other threads:[~2004-05-04 14:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-03 13:03 Buffer-local faces Miles Bader
2004-05-03 13:33 ` Miles Bader
2004-05-03 22:20 ` Richard Stallman
2004-05-03 23:19 ` Miles Bader
2004-05-04 5:56 ` Eli Zaretskii
2004-05-04 13:27 ` Stefan Monnier
2004-05-04 20:07 ` Richard Stallman
2004-05-03 22:42 ` Stefan Monnier
2004-05-03 23:27 ` Miles Bader
2004-05-04 5:45 ` Juri Linkov
2004-05-04 8:22 ` Miles Bader
2004-05-04 13:37 ` Stefan Monnier
2004-05-04 14:02 ` Miles Bader [this message]
2004-05-04 14:10 ` Stefan Monnier
2004-05-05 20:20 ` Richard Stallman
2004-05-05 20:20 ` Richard Stallman
2004-05-06 13:55 ` Miles Bader
2004-05-05 20:20 ` Richard Stallman
2004-05-05 20:43 ` Stefan Monnier
2004-05-05 8:09 ` Richard Stallman
2004-05-04 20:08 ` Richard Stallman
2004-05-04 9:18 ` David Kastrup
2004-05-04 9:57 ` Miles Bader
2004-05-04 8:40 ` Kim F. Storm
2004-05-04 9:59 ` Juri Linkov
2004-05-05 20:20 ` Richard Stallman
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=20040504140241.GB23709@fencepost \
--to=miles@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.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).