From: phillip.lord@newcastle.ac.uk (Phillip Lord)
To: 16942@debbugs.gnu.org
Subject: bug#16942: 24.3; replace-match does not return t as stated in the manual
Date: Wed, 05 Mar 2014 11:01:19 +0000 [thread overview]
Message-ID: <87wqg8j4e8.fsf@newcastle.ac.uk> (raw)
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
next reply other threads:[~2014-03-05 11:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 11:01 Phillip Lord [this message]
2014-03-06 2:11 ` bug#16942: 24.3; replace-match does not return t as stated in the manual Glenn Morris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wqg8j4e8.fsf@newcastle.ac.uk \
--to=phillip.lord@newcastle.ac.uk \
--cc=16942@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).