unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: bob@rattlesnake.com, Richard Stallman <rms@gnu.org>,
	monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: +face-remapping-20040505-0.patch
Date: 24 May 2004 10:04:14 +0200	[thread overview]
Message-ID: <m3vfimfdz5.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <20040513212808.GA7684@fencepost>

Miles Bader <miles@gnu.org> writes:

> On Mon, May 10, 2004 at 01:54:20PM -0400, Richard Stallman wrote:
> >     BTW, I think perhaps the name `face-override-alist' is a better
> >     (clearer) name than `face-remapping-alist', especially if it essentially
> >     supports the same syntax as a face property.  What do you think?
> > 
> > Don't we use the term "remapping" for other such features,
> > such as the keymap feature to remap one command into another command?
> 
> The one instance I find (via apropos) is:
> 
>    command-remapping
>      Function: Return the remapping for command COMMAND in current keymaps.
> 
> [`remap' yields the same result.]
> 
> The reasons I like override better are:
> 
>  (1) Its meaning is pretty obvious, and more visceral.  For instance I think
>      if someone didn't know about this feature, and was trying to find out
>      why their faces looked weird, they'd be more likely to chance upon or
>      recognize `override' as being the likely culprit than `remapping'.
> 
>  (2) Remapping does seem more to imply a one-to-one replacement of one face
>      name with another; if indeed the feature allows merging faces, or even
>      un-named face attributes to be used, then I think override fits better.

IMO, override also seems better than remapping in this case.

We also have e.g. overriding-local-map for buffer local bindings.

Maybe overriding-face-attribute-alist or some such...


-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2004-05-24  8:04 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-04 15:44 +face-remapping-20040505-0.patch Miles Bader
2004-05-05 20:20 ` +face-remapping-20040505-0.patch Richard Stallman
2004-05-05 22:12   ` +face-remapping-20040505-0.patch Miles Bader
2004-05-06 14:05     ` +face-remapping-20040505-0.patch Stefan Monnier
2004-05-08  1:20       ` +face-remapping-20040505-0.patch Richard Stallman
2004-05-08  1:39         ` +face-remapping-20040505-0.patch Miles Bader
2004-05-09 10:38           ` +face-remapping-20040505-0.patch Richard Stallman
2004-05-09 16:42             ` +face-remapping-20040505-0.patch Stefan Monnier
2004-05-10  0:00               ` +face-remapping-20040505-0.patch Richard Stallman
2004-05-10  0:17                 ` +face-remapping-20040505-0.patch Stefan Monnier
2004-05-10 17:54                   ` +face-remapping-20040505-0.patch Richard Stallman
2004-05-10 18:25                     ` +face-remapping-20040505-0.patch Stefan Monnier
2004-05-10 22:33                       ` +face-remapping-20040505-0.patch Miles Bader
2004-05-10 23:08                         ` +face-remapping-20040505-0.patch Stefan Monnier
2004-05-11  4:47                           ` +face-remapping-20040505-0.patch Miles Bader
2004-05-11 16:30                           ` +face-remapping-20040505-0.patch Kevin Rodgers
2004-05-12  1:30                             ` +face-remapping-20040505-0.patch Miles Bader
2004-05-10  0:42             ` +face-remapping-20040505-0.patch Miles Bader
2004-05-10 17:54               ` +face-remapping-20040505-0.patch Richard Stallman
2004-05-13 21:28                 ` +face-remapping-20040505-0.patch Miles Bader
2004-05-24  8:04                   ` Kim F. Storm [this message]
2004-05-24  8:15 ` +face-remapping-20040505-0.patch Kim F. Storm
2004-05-24  8:48   ` +face-remapping-20040505-0.patch Miles Bader
2004-05-24 10:03     ` +face-remapping-20040505-0.patch Kim F. Storm
2004-05-24 10:24       ` +face-remapping-20040505-0.patch David Kastrup
2004-05-24 17:35         ` +face-remapping-20040505-0.patch 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=m3vfimfdz5.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --cc=bob@rattlesnake.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=rms@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 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).