emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#16942: closed (24.3; replace-match does not return


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#16942: closed (24.3; replace-match does not return t as stated in the manual)
Date: Thu, 06 Mar 2014 02:12:02 +0000

Your message dated Wed, 05 Mar 2014 21:11:45 -0500
with message-id <address@hidden>
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
address@hidden)


-- 
16942: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16942
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 24.3; replace-match does not return t as stated in the manual Date: Wed, 05 Mar 2014 11:01:19 +0000

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 



--- End Message ---
--- Begin Message --- Subject: Re: bug#16942: 24.3; replace-match does not return t as stated in the manual Date: Wed, 05 Mar 2014 21:11:45 -0500 User-agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/)
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.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]