GNU bug report logs -
#15422
24.3.50; `read-string': different parameter name from `read-from-minibuffer'
Previous Next
Reported by: Drew Adams <drew.adams <at> oracle.com>
Date: Fri, 20 Sep 2013 15:04:02 UTC
Severity: minor
Found in version 24.3.50
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 15422 in the body.
You can then email your comments to 15422 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#15422
; Package
emacs
.
(Fri, 20 Sep 2013 15:04:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Drew Adams <drew.adams <at> oracle.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Fri, 20 Sep 2013 15:04:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
`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 <at> 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'
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#15422
; Package
emacs
.
(Fri, 29 Apr 2016 13:46:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 15422 <at> debbugs.gnu.org (full text, mbox):
Drew Adams <drew.adams <at> 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
bug closed, send any further explanations to
15422 <at> debbugs.gnu.org and Drew Adams <drew.adams <at> oracle.com>
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Fri, 29 Apr 2016 13:46:02 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sat, 28 May 2016 11:24:06 GMT)
Full text and
rfc822 format available.
This bug report was last modified 7 years and 342 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.