From: Eric Skoglund <eric@pagefault.se>
To: 47981@debbugs.gnu.org
Subject: bug#47981: [PATCH] Add newline and tab matching information to query-replace-regexp docstring.
Date: Fri, 23 Apr 2021 20:35:00 +0000 [thread overview]
Message-ID: <878s58yc27.fsf@pagefault.se> (raw)
[-- Attachment #1: Type: text/plain, Size: 256 bytes --]
When using query-replace-regexp to match a newline I missed the
minibuffer information to use C-q C-j instead if '\n'. I could also not
find the information in the documentation for the function.
This patch adds that information.
// Eric Skoglund
[-- Attachment #2: 0001-Add-newline-and-tab-matching-documentation-to-query-.patch --]
[-- Type: text/plain, Size: 990 bytes --]
From 542166d749ac151d401ea8eec56dbb5bafbddf45 Mon Sep 17 00:00:00 2001
From: Eric Skoglund <eric@pagefault.se>
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 | 3 +++
1 file changed, 3 insertions(+)
diff --git a/lisp/replace.el b/lisp/replace.el
index b5dea61924..970473f509 100644
--- a/lisp/replace.el
+++ b/lisp/replace.el
@@ -432,6 +432,9 @@ query-replace-regexp
of the region. Otherwise, operate from point to the end of the buffer's
accessible portion.
+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
next reply other threads:[~2021-04-23 20:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 20:35 Eric Skoglund [this message]
2021-04-24 0:10 ` bug#47981: [PATCH] Add newline and tab matching information to query-replace-regexp docstring Filipp Gunbin
2021-04-24 5:25 ` Eric Skoglund
2021-04-26 14:12 ` Filipp Gunbin
2021-04-24 6:04 ` Eli Zaretskii
2021-04-24 18:00 ` Eric Skoglund
2021-04-25 10:46 ` Stefan Kangas
2021-04-25 11:28 ` Eric Skoglund
2021-05-02 9:13 ` Lars Ingebrigtsen
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=878s58yc27.fsf@pagefault.se \
--to=eric@pagefault.se \
--cc=47981@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).