bug#15422: 24.3.50; `read-string': different parameter name from `read-from-minibuffer'

bug#15422: 24.3.50; `read-string': different parameter name from `read-from-minibuffer'

[Drew Adams]

`read-string' calls its parameter INITIAL-INPUT.
`read-from-minibuffer' calls its parameter INITIAL-CONTENTS.

But the doc string of `read-string' says that parameter INITIAL-INPUT
"behaves as in `read-from-minibuffer'", which clearly makes no sense
since `r-f-m' has no such parameter.

The two should have the same name if the doc for one refers to the
other.



In GNU Emacs 24.3.50.1 (i686-pc-mingw32)
 of 2013-08-31 on ODIEONE
Bzr revision: 114088 rgm@gnu.org-20130901021232-sazo0qla2qgcko95
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --prefix=/c/Devel/emacs/binary --enable-checking=yes,glyphs
 'CFLAGS=-O0 -g3' LDFLAGS=-Lc:/Devel/emacs/lib
 CPPFLAGS=-Ic:/Devel/emacs/include'

bug#15422: 24.3.50; `read-string': different parameter name from `read-from-minibuffer'

[Lars Ingebrigtsen]

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

> `read-string' calls its parameter INITIAL-INPUT.
> `read-from-minibuffer' calls its parameter INITIAL-CONTENTS.
>
> But the doc string of `read-string' says that parameter INITIAL-INPUT
> "behaves as in `read-from-minibuffer'", which clearly makes no sense
> since `r-f-m' has no such parameter.
>
> The two should have the same name if the doc for one refers to the
> other.

Somebody has sneakily changed the doc string:

If non-nil, second arg INITIAL-INPUT is a string to insert before reading.
  This argument has been superseded by DEFAULT-VALUE and should normally be nil
  in new code.  It behaves as INITIAL-CONTENTS in ‘read-from-minibuffer’ (which
  see).


-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no