unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
Cc: emacs-devel@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
	Miles Bader <miles@gnu.org>
Subject: Re: Buffer-local faces
Date: Tue, 4 May 2004 04:22:36 -0400	[thread overview]
Message-ID: <20040504082236.GA21306@fencepost> (raw)
In-Reply-To: <87hduwyccu.fsf@mail.jurta.org>

On Tue, May 04, 2004 at 08:45:21AM +0300, Juri Linkov wrote:
> Then subtracting face attributes would be useful too.  For example,
> using the `-' symbol before the face name could remove its attributes
> from the composed face, e.g. using (region region - bold) to remove
> all attributes of the `bold' face whose values are equal to attribute
> values of the `region' face.  This may complicate things, but this
> is no less useful than merging faces.

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....

Morever, I don't think would help in this case because face-merging more
specific faces during redisplay will always override the default attributes.

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.

[Since the face-remapping code just uses normal face merging, this feature
would work with that too, but it wouldn't be specific to it.]

Generally useful?  I'm not sure, but it could probably handle the `no bold
please' case.

-Miles
-- 
"Whatever you do will be insignificant, but it is very important that
 you do it."  Mahatma Ghandi

  reply	other threads:[~2004-05-04  8:22 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 [this message]
2004-05-04 13:37         ` Stefan Monnier
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=20040504082236.GA21306@fencepost \
    --to=miles@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).