From d8f1d2f3a332de2722a5eb6acb460369b2b11507 Mon Sep 17 00:00:00 2001 From: Juanma Barranquero Date: Mon, 19 Nov 2007 12:10:41 +0000 Subject: [PATCH] (map-query-replace-regexp): Doc fix (revert part of 2000-05-21T17:04:47Z!fx@gnu.org made on 2000-05-21 with no ChangeLog entry). --- lisp/ChangeLog | 5 +++++ lisp/replace.el | 8 +++----- 2 files changed, 8 insertions(+), 5 deletions(-) diff --git a/lisp/ChangeLog b/lisp/ChangeLog index d67753b2b41..a567708602c 100644 --- a/lisp/ChangeLog +++ b/lisp/ChangeLog @@ -1,3 +1,8 @@ +2007-11-19 Juanma Barranquero + + * replace.el (map-query-replace-regexp): Doc fix (revert part of + 2000-05-21T17:04:47Z!fx@gnu.org made on 2000-05-21 with no ChangeLog entry). + 2007-11-19 Dan Nicolaescu * progmodes/octave-mod.el (inferior-octave-send-list-and-digest): diff --git a/lisp/replace.el b/lisp/replace.el index 8e02ee3b347..8b2c3b92399 100644 --- a/lisp/replace.el +++ b/lisp/replace.el @@ -372,11 +372,9 @@ using `search-forward-regexp' and `replace-match' is preferred." "22.1") (defun map-query-replace-regexp (regexp to-strings &optional n start end) "Replace some matches for REGEXP with various strings, in rotation. -The second argument TO-STRINGS contains the replacement strings, -separated by spaces. Third arg DELIMITED (prefix arg if interactive), -if non-nil, means replace only matches surrounded by word boundaries. -This command works like `query-replace-regexp' except that each -successive replacement uses the next successive replacement string, +The second argument TO-STRINGS contains the replacement strings, separated +by spaces. This command works like `query-replace-regexp' except that +each successive replacement uses the next successive replacement string, wrapping around from the last such string to the first. In Transient Mark mode, if the mark is active, operate on the contents -- 2.39.2