summaryrefslogtreecommitdiff
path: root/lisp/replace.el
diff options
context:
space:
mode:
authorLars Ingebrigtsen <larsi@gnus.org>2016-04-30 20:21:11 +0200
committerLars Ingebrigtsen <larsi@gnus.org>2016-04-30 20:32:56 +0200
commit139874ba53c2e2de9868f8e5234d6ea2bcb97af8 (patch)
tree5ffd7496361c4634796a96547d60bc75a935ec8f /lisp/replace.el
parent921b40476f597c84d7c34aa289cd43caeb389c4a (diff)
downloademacs-139874ba53c2e2de9868f8e5234d6ea2bcb97af8.tar.gz
replace-match-maybe-edit doc clarification
* lisp/replace.el (replace-match-maybe-edit): Say what MATCH-DATA is (bug#20304).
Diffstat (limited to 'lisp/replace.el')
-rw-r--r--lisp/replace.el4
1 files changed, 3 insertions, 1 deletions
diff --git a/lisp/replace.el b/lisp/replace.el
index 91e5db818f9..c44d1f0f8cb 100644
--- a/lisp/replace.el
+++ b/lisp/replace.el
@@ -2001,7 +2001,9 @@ but coerced to the correct value of INTEGERS."
FIXEDCASE, LITERAL are passed to `replace-match' (which see).
After possibly editing it (if `\\?' is present), NEWTEXT is also
passed to `replace-match'. If NOEDIT is true, no check for `\\?'
-is made (to save time). MATCH-DATA is used for the replacement.
+is made (to save time).
+MATCH-DATA is used for the replacement, and is a data structure
+as returned from the `match-data' function.
In case editing is done, it is changed to use markers. BACKWARD is
used to reverse the replacement direction.