Subject: bug#47981: [PATCH] Add newline and tab matching information to query-replace-regexp docstring.

From: Eric Skoglund <[email-masked]>
Date: Sat, 24 Apr 2021 18:00:22 +0000

"Eli Zaretskii" <[email-masked]> writes:

>> +Matching a newline with `\n' will not work, use `C-q C-j' instead.
>> +Similarly to match a tab character (`\t') just press `TAB'.
>
> That's only true in interactive invocations, isn't it?

Yes you are right, here's an updated version that clarifies that.

// Eric Skoglund

From de9dccf31500ed896296ea11c7b4740c1c7a17ea Mon Sep 17 00:00:00 2001
From: Eric Skoglund <[email-masked]>
Date: Fri, 23 Apr 2021 22:10:07 +0200
Subject: [PATCH] Add newline and tab matching documentation to
 query-replace-regexp

* lisp/replace.el: Add \n and \t matching information to
query-replace-regexp docstring.
---
 lisp/replace.el | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/lisp/replace.el b/lisp/replace.el
index b5dea61924..81c465eb7f 100644
--- a/lisp/replace.el
+++ b/lisp/replace.el
@@ -432,6 +432,10 @@ query-replace-regexp
 of the region.  Otherwise, operate from point to the end of the buffer's
 accessible portion.
 
+When invoked interactivly, Matching a newline with `\n' will not work,
+use `C-q C-j' instead.  Similarly to match a tab character (`\t')
+just press `TAB'.
+
 Use \\<minibuffer-local-map>\\[next-history-element] \
 to pull the last incremental search regexp to the minibuffer
 that reads REGEXP, or invoke replacements from
-- 
2.30.2