procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

* minibuf.texi: Clarify history list discussion (Bug#8085).

Browse source
This commit is contained in:
Chong Yidong 2011-02-27 17:10:48 -05:00
parent 6c89f663ba
commit b923f7a98f
2 changed files with 14 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
doc/lispref/ChangeLog
View file

@ -1,3 +1,8 @@
2011-02-27 Chong Yidong <cyd@stupidchicken.com>
* minibuf.texi (Minibuffer History): Clarify discussion of
minibuffer history lists (Bug#8085).
2011-02-19 Eli Zaretskii <eliz@gnu.org>
* elisp.texi: Sync @dircategory with ../../info/dir.

19
doc/lispref/minibuf.texi
View file

@ -433,18 +433,17 @@ expression, thus moving point forward one word.
@cindex minibuffer history
@cindex history list
A @dfn{minibuffer history list} records previous minibuffer inputs so
the user can reuse them conveniently. A history list is actually a
symbol, not a list; it is a variable whose value is a list of strings
(previous inputs), most recent first.
A @dfn{minibuffer history list} records previous minibuffer inputs
so the user can reuse them conveniently. It is a variable whose value
is a list of strings (previous inputs), most recent first.
There are many separate history lists, used for different kinds of
inputs. It's the Lisp programmer's job to specify the right history
list for each use of the minibuffer.
There are many separate minibuffer history lists, used for different
kinds of inputs. It's the Lisp programmer's job to specify the right
history list for each use of the minibuffer.
You specify the history list with the optional @var{hist} argument
to either @code{read-from-minibuffer} or @code{completing-read}. Here
are the possible values for it:
You specify a minibuffer history list with the optional @var{hist}
argument to @code{read-from-minibuffer} or @code{completing-read}.
Here are the possible values for it:
@table @asis
@item @var{variable}