From: Juri Linkov <juri@jurta.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: Kevin Rodgers <kevin.d.rodgers@gmail.com>, 10885@debbugs.gnu.org
Subject: bug#10885: Replace expressions: enhance functionality when searching in filled paragraphs
Date: Sun, 11 Mar 2012 12:48:08 +0200 [thread overview]
Message-ID: <8762ebbehj.fsf@mail.jurta.org> (raw)
In-Reply-To: <CAH8Pv0j2Q8tyXTN7ee4phqW2ZqSVwoc=xv=B6b2YMtQAaLbxQA@mail.gmail.com> (Dani Moncayo's message of "Sun, 11 Mar 2012 09:59:07 +0100")
>> There is one problem of using `search-whitespace-regexp'
>> in `query-replace-regexp'.
>>
>> When the user doesn't want `SPC' to match any sequence of whitespace
>> characters in regexp isearch `C-M-s', it it possible to type `C-q SPC'.
>>
>> But how to do the same in `query-replace-regexp'?
>>
>> `C-M-% replace C-q SPC this' doesn't quote SPC as a literal character.
>
> FWIW: the isearch commands have this problem too, when editing the
> search string from the minibuffer.
>
> For example: C-M-s replace this M-e M-b DEL C-q SPC RET
> --> The new search string doesn't have the intended quoted space.
Actually this `search-spaces-regexp' thing is rather a feature of word search
intermixed with the pure regexp search into the hybrid half-word/regexp search.
What `C-q SPC' does is adding the invisible regexp `[ ]' to the search string.
In the minibuffer `C-q SPC' could do the same, not necessarily invisibly
because you still see `[ ]' when typing e.g. `C-M-s replace C-q SPC this M-e'
next prev parent reply other threads:[~2012-03-11 10:48 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-26 1:02 bug#10885: Replace expressions: enhance functionality when searching in filled paragraphs linuxfever
2012-02-26 1:57 ` Glenn Morris
2012-02-26 7:16 ` Kevin Rodgers
2012-02-28 10:04 ` Dani Moncayo
2012-02-28 10:09 ` Dani Moncayo
2012-02-28 10:42 ` Juri Linkov
2012-02-29 0:12 ` Glenn Morris
2012-02-29 0:41 ` Juri Linkov
2012-03-11 8:59 ` Dani Moncayo
2012-03-11 10:48 ` Juri Linkov [this message]
2012-09-02 9:45 ` Juri Linkov
2012-09-02 11:32 ` Juri Linkov
2012-09-05 8:38 ` Juri Linkov
2012-09-05 14:38 ` Stefan Monnier
2012-09-06 8:54 ` Juri Linkov
2012-09-06 15:54 ` Dani Moncayo
2012-09-06 16:50 ` Juri Linkov
2012-09-06 17:39 ` Dani Moncayo
2012-09-06 19:11 ` Juri Linkov
2012-09-06 19:15 ` Juri Linkov
2012-09-06 19:45 ` Dani Moncayo
2012-09-06 20:21 ` Dani Moncayo
2012-09-06 21:25 ` Stefan Monnier
2012-09-07 8:33 ` Dani Moncayo
2012-09-07 9:28 ` Juri Linkov
2012-09-09 22:15 ` Juri Linkov
2012-09-05 14:39 ` Stefan Monnier
2012-02-26 10:10 ` linuxfever
2012-02-26 21:22 ` Stefan Monnier
2012-02-26 10:17 ` Dani Moncayo
2012-02-27 10:58 ` Juri Linkov
2012-02-27 13:27 ` Dani Moncayo
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=8762ebbehj.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=10885@debbugs.gnu.org \
--cc=dmoncayo@gmail.com \
--cc=kevin.d.rodgers@gmail.com \
/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).