GNU bug report logs -
#16942
24.3; replace-match does not return t as stated in the manual
Previous Next
Reported by: phillip.lord <at> newcastle.ac.uk (Phillip Lord)
Date: Wed, 5 Mar 2014 16:43:02 UTC
Severity: minor
Found in version 24.3
Fixed in version 24.4
Done: Glenn Morris <rgm <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Wed, 05 Mar 2014 21:11:45 -0500
with message-id <ofob1krs7y.fsf <at> fencepost.gnu.org>
and subject line Re: bug#16942: 24.3; replace-match does not return t as stated in the manual
has caused the debbugs.gnu.org bug report #16942,
regarding 24.3; replace-match does not return t as stated in the manual
to be marked as done.
(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)
--
16942: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16942
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
This is a small documentation bug.
From info node: `(elisp) Replacing Match'
If you did the last search in a buffer, you should omit the STRING
argument or specify `nil' for it, and make sure that the current
buffer is the one in which you performed the last search. Then
this function edits the buffer, replacing the matched text with
REPLACEMENT. It leaves point at the end of the replacement text,
and returns `t'.
In my hands, replace-match returns nil regardless. The docstring does
not mention the return type.
Phil
[Message part 3 (message/rfc822, inline)]
Version: 24.4
Phillip Lord wrote:
>>From info node: `(elisp) Replacing Match'
>
> If you did the last search in a buffer, you should omit the STRING
> argument or specify `nil' for it, and make sure that the current
> buffer is the one in which you performed the last search. Then
> this function edits the buffer, replacing the matched text with
> REPLACEMENT. It leaves point at the end of the replacement text,
> and returns `t'.
>
> In my hands, replace-match returns nil regardless. The docstring does
> not mention the return type.
I simply undocumented the return value, since it was both uninteresting
and wrong.
This bug report was last modified 11 years and 138 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.