From c51943d71d99b7196957292e2cf9a9c554ec4d21 Mon Sep 17 00:00:00 2001 From: Glenn Morris Date: Thu, 28 Jan 2016 17:45:50 -0500 Subject: [PATCH] * lisp/custom.el (defcustom): Doc fix. * doc/lispref/customize.texi (Variable Definitions): Defcustom should always have a type. --- doc/lispref/customize.texi | 3 ++- lisp/custom.el | 1 + 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/lispref/customize.texi b/doc/lispref/customize.texi index 1f207dce823..994c346331f 100644 --- a/doc/lispref/customize.texi +++ b/doc/lispref/customize.texi @@ -334,7 +334,8 @@ macro accepts the following keywords: @item :type @var{type} Use @var{type} as the data type for this option. It specifies which values are legitimate, and how to display the value -(@pxref{Customization Types}). +(@pxref{Customization Types}). Every @code{defcustom} should specify +a value for this keyword. @item :options @var{value-list} @kindex options@r{, @code{defcustom} keyword} diff --git a/lisp/custom.el b/lisp/custom.el index f84aed2b135..550ba440c0f 100644 --- a/lisp/custom.el +++ b/lisp/custom.el @@ -224,6 +224,7 @@ The remaining arguments to `defcustom' should have the form The following keywords are meaningful: :type VALUE should be a widget type for editing the symbol's value. + Every `defcustom' should specify a value for this keyword. :options VALUE should be a list of valid members of the widget type. :initialize VALUE should be a function used to initialize the