From: Richard M. Stallman <rms@gnu.org>
Date: Mon, 14 Feb 2005 10:17:32 +0000 (+0000)
Subject: (Text from Minibuffer): Minor clarification.
X-Git-Tag: ttn-vms-21-2-B4~2305
X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=e37d6e4c86bad93161edcc5f52594e6d26662eda;p=emacs.git

(Text from Minibuffer): Minor clarification.
Mention arrow keys.
---

diff --git a/lispref/minibuf.texi b/lispref/minibuf.texi
index 1455c63fe34..0e855b499ae 100644
--- a/lispref/minibuf.texi
+++ b/lispref/minibuf.texi
@@ -111,7 +111,8 @@ was supplied when Emacs was started.
   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 @@ default, it makes the following bindings:
 @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}