unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Juri Linkov <juri@jurta.org>, emacs-devel@gnu.org
Subject: Re: Buffer-local faces
Date: 04 May 2004 09:37:52 -0400	[thread overview]
Message-ID: <m14qqw1fqd.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <20040504082236.GA21306@fencepost>

> 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 ...
But supposedly withing RGB this doesn't work so well, so maybe it would be
better to do it on CYK colors.  In any case this is for post-release.

> A _different_ feature that might work is a way to mark a face attribute as
> `non overridable'.  For instance if a face attribute could be a list like
> (fixed VALUE), where VALUE is a normal value for that attribute, face
> merging would always use the `base' value for that attribute instead of the
> `normally overriding' value.

A related question is how to make a face that uses explicitly the default
font.  E.g. let's say my header-line face uses helvetica font and I want to
put text in the header-line that uses the same font as the default font.
Right now, the best I could come up with is to extract the font of `default'
and pass it to `myface', but that's done "statically".

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.


        Stefan

  reply	other threads:[~2004-05-04 13:37 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 [this message]
2004-05-04 14:02           ` Miles Bader
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=m14qqw1fqd.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --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).