Commit 5890344b authored by Chong Yidong's avatar Chong Yidong
Browse files

* display.texi: Revert 2005-11-20 change.

parent 0268cef3
2005-11-20 Chong Yidong <>
* display.texi: Revert 2005-11-20 change.
2005-11-20 Thien-Thi Nguyen <>
* processes.texi (Bindat Functions):
......@@ -1859,11 +1859,6 @@ the first face fails to specify a particular attribute, that means the
next face gets a chance. However, the @code{default} face must
specify all attributes.
Any attribute can have the value @code{:ignore-defface}. The effect
of this is identical to @code{unspecified}. It exists because of an
technical ambiguity in giving attributes the value @code{unspecified}.
@xref{Attribute Functions}.
Some of these font attributes are meaningful only on certain kinds of
displays---if your display cannot handle a certain attribute, the
attribute is ignored. (The attributes @code{:family}, @code{:width},
......@@ -2056,14 +2051,6 @@ This function sets one or more attributes of face @var{face}
for frame @var{frame}. If @var{frame} is @code{nil}, it sets
the attribute for all frames, and the defaults for new frames.
Unless you know what you're doing, don't set an attribute to
@code{unspecified}. This is ambiguous---it is unclear whether it
means to unspecify the value stored in the frame-local copies of the
face (which means reverting to the original face spec), or the value
in the face spec itself. What you probably want is to set the
attribute to @code{:ignore-defface}. This forces the attribute value
to be acquired from some other face during face merging.
The extra arguments @var{arguments} specify the attributes to set, and
the values for them. They should consist of alternating attribute names
(such as @code{:family} or @code{:underline}) and corresponding values.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment