bug#8085: 24.0.50; (emacs) Minibuffer History

bug#8085: 24.0.50; (emacs) Minibuffer History

[Drew Adams]

This part of the node (second sentence) is not quite correct:
 
"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."
 
That's true except for one exception AFAIK (are there others?):
`command-history'.  It's value is a list of sexps, not a list of
strings.
 
I don't know what the best bug fix is.  Dunno whether this should be
mentioned or not, but it is not really the case that the HISTORY arg to
`read-from-minibuffer' and `completing-read' must be a variable whose
value is a list of strings.  This is a bit surprising, but a list of
non-strings also "works" in some ways.
 
Maybe this should be passed over in silence - dunno.
 
 
 
In GNU Emacs 24.0.50.1 (i386-mingw-nt5.1.2600)
 of 2011-02-14 on 3249CTO
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (4.4) --no-opt --cflags
-Ic:/imagesupport/include'
 

bug#8085: 24.0.50; (emacs) Minibuffer History

[Chong Yidong]

"Drew Adams" <drew.adams@oracle.com> writes:

> "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."
>
> That's true except for one exception AFAIK (are there others?):
> `command-history'.  It's value is a list of sexps, not a list of
> strings.

The sentence is referring to minibuffer history lists; command-history
is not one.  I've tweaked the documentation to make this clearer.