From 388bb723fa078158d3148de05e942f9c01e95dd8 Mon Sep 17 00:00:00 2001 From: Lars Ingebrigtsen Date: Thu, 28 Apr 2016 00:53:04 +0200 Subject: [PATCH] Add some concept index entries for custom types * doc/lispref/customize.texi (Composite Types): Add concept index entries for restricted-sexp, radio and choice (bug#7385). --- doc/lispref/customize.texi | 3 +++ 1 file changed, 3 insertions(+) diff --git a/doc/lispref/customize.texi b/doc/lispref/customize.texi index 994c346331..14e6eb3ab2 100644 --- a/doc/lispref/customize.texi +++ b/doc/lispref/customize.texi @@ -841,6 +841,7 @@ most general last. Here's an example of proper usage: This way, the special value @code{nil} is not treated like other symbols, and symbols are not treated like other Lisp expressions. +@cindex radio, customization types @item (radio @var{element-types}@dots{}) This is similar to @code{choice}, except that the choices are displayed using radio buttons rather than a menu. This has the advantage of @@ -936,6 +937,7 @@ The value must be a list and each element of the list must fit the type list of elements, with @samp{[INS]} and @samp{[DEL]} buttons for adding more elements or removing elements. +@cindex restricted-sexp, customization types @item (restricted-sexp :match-alternatives @var{criteria}) This is the most general composite type construct. The value may be any Lisp object that satisfies one of @var{criteria}. @var{criteria} @@ -1020,6 +1022,7 @@ and whose remaining arguments should be zero or more of @code{foo} and This matches values such as @code{(baz)}, @code{(baz foo)}, @code{(baz bar)} and @code{(baz foo bar)}. +@cindex choice, customization types When the element-type is a @code{choice}, you use @code{:inline} not in the @code{choice} itself, but in (some of) the alternatives of the @code{choice}. For example, to match a list which must start with a -- 2.39.2