Give example of using special-display-buffer-names to specify frame parameters.

diff --git a/lispref/windows.texi b/lispref/windows.texi
index 1fc7a7e5022a69faa42123054fa5af07d955f7ba..f43a792f3be8b0247c2b6f59861f19d69cd67fbd 100644 (file)
--- a/lispref/windows.texi
+++ b/lispref/windows.texi
@@ -960,11 +960,22 @@ buffer specially.
 By default, special display means to give the buffer a dedicated frame.
 
 If an element is a list, instead of a string, then the @sc{car} of the
-list is the buffer name, and the rest of the list says how to create the
-frame.  There are two possibilities for the rest of the list.  It can be
-an alist, specifying frame parameters, or it can contain a function and
-arguments to give to it.  (The function's first argument is always the
-buffer to be displayed; the arguments from the list come after that.)
+list is the buffer name, and the rest of the list says how to create
+the frame.  There are two possibilities for the rest of the list (its
+@sc{cdr}).  It can be an alist, specifying frame parameters, or it can
+contain a function and arguments to give to it.  (The function's first
+argument is always the buffer to be displayed; the arguments from the
+list come after that.)
+
+For example:
+
+@example
+(("myfile" (minibuffer) (menu-bar-lines . 0)))
+@end example
+
+@noindent
+specifies to display a buffer named @samp{myfile} in a dedicated frame
+with specified @code{minibuffer} and @code{menu-bar-lines} parameters.
 @end defopt
 
 @defopt special-display-regexps