From b74f585b6b787349a5a0dda29fe788baa0f3d6c9 Mon Sep 17 00:00:00 2001 From: "Richard M. Stallman" Date: Wed, 8 Jun 2005 15:33:10 +0000 Subject: (Defining Faces): Explain that face name should not end in `-face'. --- lispref/display.texi | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) (limited to 'lispref') diff --git a/lispref/display.texi b/lispref/display.texi index 890c636b2f..87520fb4d4 100644 --- a/lispref/display.texi +++ b/lispref/display.texi @@ -1795,14 +1795,15 @@ end of a line. The way to define a new face is with @code{defface}. This creates a kind of customization item (@pxref{Customization}) which the user can customize using the Customization buffer (@pxref{Easy Customization,,, -emacs, The GNU Emacs Manual}). +emacs, The GNU Emacs Manual}). @defmac defface face spec doc [keyword value]... -This declares @var{face} as a customizable face that defaults according -to @var{spec}. You should not quote the symbol @var{face}. The +This declares @var{face} as a customizable face that defaults +according to @var{spec}. You should not quote the symbol @var{face}, +and it should not end in @samp{-face} (that would be redundant). The argument @var{doc} specifies the face documentation. The keywords you -can use in @code{defface} are the same ones that are meaningful in both -@code{defgroup} and @code{defcustom} (@pxref{Common Keywords}). +can use in @code{defface} are the same as in @code{defgroup} and +@code{defcustom} (@pxref{Common Keywords}). When @code{defface} executes, it defines the face according to @var{spec}, then uses any customizations that were read from the -- cgit v1.2.3