comparison lispref/customize.texi @ 90197:b7da78284d4c

Revision: miles@gnu.org--gnu-2005/emacs--unicode--0--patch-65 Merge from emacs--cvs-trunk--0 Patches applied: * emacs--cvs-trunk--0 (patch 425-445) - Remove "-face" suffix from gnus faces - Update from CVS - Remove "-face" suffix from MH-E faces - Remove "-face" suffix from cc-mode faces - Remove "-face" suffix from eshell faces - Remove "-face" suffix from ediff faces - Implement tty vertical-divider face - Rename vertical-divider face to vertical-border - Change escape-glyph color on dark backgrounds back to cyan - Update reference to renamed Buffer-menu-buffer face
author Miles Bader <miles@gnu.org>
date Fri, 24 Jun 2005 01:59:52 +0000
parents 62afea0771d8 99e9892a51d9
children fbb2bea03df9
comparison
equal deleted inserted replaced
90196:82d495f87e7b 90197:b7da78284d4c
656 customize will choose the first alternative that the value fits. This 656 customize will choose the first alternative that the value fits. This
657 means you should always list the most specific types first, and the 657 means you should always list the most specific types first, and the
658 most general last. Here's an example of proper usage: 658 most general last. Here's an example of proper usage:
659 659
660 @example 660 @example
661 (choice (const :tag "Off" nil) symbol (sexp :tag "Other")) 661 (choice (const :tag "Off" nil)
662 symbol (sexp :tag "Other"))
662 @end example 663 @end example
663 664
664 @noindent 665 @noindent
665 This way, the special value @code{nil} is not treated like other 666 This way, the special value @code{nil} is not treated like other
666 symbols, and symbols are not treated like other Lisp expressions. 667 symbols, and symbols are not treated like other Lisp expressions.