# HG changeset patch
# User Richard M. Stallman <rms@gnu.org>
# Date 1108376252 0
# Node ID 114da1fc3775a539058bb462c6329d4ec87cd5ee
# Parent  123a4dbb8a877b864ab4c6a49553bcb2f55a5bb3
(Text from Minibuffer): Minor clarification.
Mention arrow keys.

diff -r 123a4dbb8a87 -r 114da1fc3775 lispref/minibuf.texi
--- a/lispref/minibuf.texi	Mon Feb 14 10:16:24 2005 +0000
+++ b/lispref/minibuf.texi	Mon Feb 14 10:17:32 2005 +0000
@@ -111,7 +111,8 @@
   Most often, the minibuffer is used to read text as a string.  It can
 also be used to read a Lisp object in textual form.  The most basic
 primitive for minibuffer input is @code{read-from-minibuffer}; it can do
-either one.
+either one.  There are also specialized commands for reading
+commands, variables, file names, etc. (@pxref{Completion}).
 
   In most cases, you should not call minibuffer input functions in the
 middle of a Lisp function.  Instead, do all minibuffer input as part of
@@ -234,9 +235,11 @@
 @code{abort-recursive-edit}
 
 @item @kbd{M-n}
+@itemx @key{DOWN}
 @code{next-history-element}
 
 @item @kbd{M-p}
+@itemx @key{UP}
 @code{previous-history-element}
 
 @item @kbd{M-s}