aboutsummaryrefslogtreecommitdiffstats
path: root/lispref/minibuf.texi
diff options
context:
space:
mode:
authorRichard M. Stallman <[email protected]>2005-02-14 10:17:32 +0000
committerRichard M. Stallman <[email protected]>2005-02-14 10:17:32 +0000
commite37d6e4c86bad93161edcc5f52594e6d26662eda (patch)
tree47e997d5e6410c76727e09d1ac154f1e710e173a /lispref/minibuf.texi
parent9e328e231a6f97b580de43102bf1730e4c4b9cbf (diff)
(Text from Minibuffer): Minor clarification.
Mention arrow keys.
Diffstat (limited to 'lispref/minibuf.texi')
-rw-r--r--lispref/minibuf.texi5
1 files changed, 4 insertions, 1 deletions
diff --git a/lispref/minibuf.texi b/lispref/minibuf.texi
index 1455c63fe3..0e855b499a 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}