[Emacs-diffs] master adb9dc4: Document :match-inline widget elements

[Lars Ingebrigtsen]

branch: master
commit adb9dc4bff72c390175ddb97f8cc72afee9ee589
Author: Lars Ingebrigtsen <address@hidden>
Commit: Lars Ingebrigtsen <address@hidden>

    Document :match-inline widget elements
    
    * doc/lispref/customize.texi (Type Keywords): Document
    :match-inline (bug#8716).
    (Splicing into Lists): Mention :match-inline.
---
 doc/lispref/customize.texi | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/doc/lispref/customize.texi b/doc/lispref/customize.texi
index 822066f..64c06c2 100644
--- a/doc/lispref/customize.texi
+++ b/doc/lispref/customize.texi
@@ -1047,6 +1047,9 @@ overall list has two elements and the second element is 
@code{t}.  If
 the user chooses the second alternative, then the overall list has three
 elements and the second and third must be strings.
 
+  The widgets can specify predicates to say whether an inline value
+matches the widget with the @code{:match-inline} element.
+
 @node Type Keywords
 @subsection Type Keywords
 
@@ -1165,6 +1168,14 @@ corresponding value, @var{function}, should be a 
function that accepts
 two arguments, a widget and a value; it should return non-@code{nil} if
 the value is acceptable.
 
+@item :match-inline @var{function}
+@kindex match-inline@r{, customization keyword}
+Specify how to decide whether an inline value matches the type.  The
+corresponding value, @var{function}, should be a function that accepts
+two arguments, a widget and an inline value; it should return
+non-@code{nil} if the value is acceptable.  See @ref{Splicing into
+Lists} for more information about inline values.
+
 @item :validate @var{function}
 Specify a validation function for input.  @var{function} takes a
 widget as an argument, and should return @code{nil} if the widget's