@comment node-name, next, previous, up
@top The Customization Library
-Version: 1.65
+Version: 1.70
@menu
* Introduction::
It is possible to specify that a face should have different attributes
on different device types. For example, a face may make text red on a
-color device, and bold on a monochrome device.
+color device, and bold on a monochrome device. You do this by
+activating `Edit All' in the state menu.
The way this is presented in the customization buffer is to have a list
of display specifications, and for each display specification a list of
@example
*** custom-invalid-face: (sample)
+ State: this item is unchanged from its factory setting.
[ ] Face used when the customize item is invalid.
- [INS] [DEL] Display: [ ] Type: [ ] X [ ] TTY
+ [INS] [DEL] Display: [ ] Type: [ ] X [ ] PM [ ] Win32 [ ] DOS [ ] TTY
[X] Class: [X] Color [ ] Grayscale [ ] Monochrome
[ ] Background: [ ] Light [ ] Dark
Attributes: [ ] Bold: off
@end example
This has two display specifications. The first will match all color
-displays, independently on whether the device is X11 or a tty, and
+displays, independently on what window system the device belongs to, and
whether background color is dark or light. For devices matching this
specification, @samp{custom-invalid-face} will force text to be
displayed in yellow on red, but leave all other attributes alone.
the check boxes. The first checkbox in each line in the display
specification is special. It specify whether this particular property
will even be relevant. By not checking the box in the first display, we
-match all device types, also device types other than X11 and tty, for
-example ms-windows, nextstep, and mac os.
+match all device types, also device types other than those listed.
After modifying the face, you can activate the state button to make the
changes take effect. The menu items in the state button menu is similar
When you save the customizations, call to @code{custom-set-variables},
@code{custom-set-faces} are inserted into the file specified by
@code{custom-file}. By default @code{custom-file} is your @file{.emacs}
-file. The two functions will initialize variables and faces as you have
-specified.
+file. If you use another file, you must explicitly load it yourself.
+The two functions will initialize variables and faces as you have
+specified.
@node Wishlist, , The Init File, Top
@comment node-name, next, previous, up
should not be allowed to select the @samp{Factory} menu item.
@item
-We need @strong{much} better support for keyboard operations in the
-customize buffer.
+Better support for keyboard operations in the customize buffer.
@item
Integrate with @file{w3} so you can customization buffers with much
Support selectable color themes. I.e., change many faces by setting one
variable.
-@item
-There should be a way to see only the "current" display when editing a
-face, and that should be "on" by default.
-
@item
Support undo using lmi's @file{gnus-undo.el}.
Suggested by Jens Lautenbacher
@samp{<jens@@lemming0.lem.uni-karlsruhe.de>}.@refill
+@item
+Use @file{font.el} to extract font attributes from rogue faces.
+
+@item
+Empty customization groups should start open (harder than it looks).
+
@end itemize
@contents