From: Dani Moncayo <dmoncayo@gmail.com>
To: 13480@debbugs.gnu.org
Subject: bug#13480: 24.3.50; `C-w' from Isearch should translate newlines to spaces
Date: Thu, 17 Jan 2013 21:39:29 +0100 [thread overview]
Message-ID: <CAH8Pv0iwpPs-67rnTVK7e9+8E518joTpKCXa=YGOGvdCz1-s5g@mail.gmail.com> (raw)
Hello,
I have `isearch-lax-whitespace' set to t in my init file, so that I
can search for a sequence of words regardless of whether there is line
breaks or plain spaces between them.
Now, if the text following point is "foo bar" and I do `C-s C-w C-w'
I'll be searching for any sequence of those two words, separated by
any whitespace (well, controlled by `search-whitespace-regexp'). Ok,
as expected.
But I've just noticed that if the text following point is
"foo<newline>bar" and I do the same, I'll be searching exactly for
that fixed sequence of 7 characters, including the <newline>. Not
what I want, obviously.
So I propose that the command `isearch-yank-word-or-char' (C-w in
Isearch) DTRT in this case, i.e., when `search-whitespace-regexp' is
non-nil, translate the <newline> into a simple space when pulling text
from the buffer into the search string.
TIA.
In GNU Emacs 24.3.50.1 (i386-mingw-nt6.2.9200)
of 2013-01-10 on MS-W8-DANI
Bzr revision: 111476 jan.h.d@swipnet.se-20130110174508-0pdaxa5ys9me698g
Windowing system distributor `Microsoft Corp.', version 6.2.9200
Configured using:
`configure --with-gcc (4.7) --no-opt --enable-checking --cflags
-Ic:/emacs/libs/libXpm-3.5.10/include -Ic:/emacs/libs/libXpm-3.5.10/src
-Ic:/emacs/libs/libpng-dev_1.4.3-1_win32/include
-Ic:/emacs/libs/zlib-dev_1.2.5-2_win32/include
-Ic:/emacs/libs/giflib-4.1.4-1-lib/include
-Ic:/emacs/libs/jpeg-6b-4-lib/include
-Ic:/emacs/libs/tiff-3.8.2-1-lib/include
-Ic:/emacs/libs/libxml2-2.7.8-w32-bin/include/libxml2
-Ic:/emacs/libs/gnutls-3.1.5-w32/include
-Ic:/emacs/libs/libiconv-1.14-2-mingw32-dev/include'
--
Dani Moncayo
next reply other threads:[~2013-01-17 20:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 20:39 Dani Moncayo [this message]
2013-01-17 21:27 ` bug#13480: 24.3.50; `C-w' from Isearch should translate newlines to spaces Juri Linkov
2013-01-17 23:10 ` Dani Moncayo
2013-01-17 23:54 ` Dani Moncayo
2013-01-18 21:59 ` Juri Linkov
2013-01-19 8:05 ` Dani Moncayo
2013-01-19 9:56 ` Dani Moncayo
2013-01-19 10:07 ` Juri Linkov
2013-01-19 10:40 ` Dani Moncayo
2013-01-19 10:57 ` Juri Linkov
2013-01-19 12:11 ` Dani Moncayo
2013-01-19 15:45 ` Drew Adams
2013-01-19 15:43 ` Drew Adams
2013-01-19 17:20 ` Stefan Monnier
2013-01-19 23:30 ` Juri Linkov
2013-01-20 9:41 ` Dani Moncayo
2013-01-20 12:27 ` Dani Moncayo
2022-04-22 12:28 ` Lars Ingebrigtsen
2022-04-24 15:46 ` Juri Linkov
2022-04-25 7:26 ` Lars Ingebrigtsen
2013-01-19 15:01 ` Drew Adams
2013-01-19 9:59 ` Juri Linkov
2013-08-03 17:09 ` 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='CAH8Pv0iwpPs-67rnTVK7e9+8E518joTpKCXa=YGOGvdCz1-s5g@mail.gmail.com' \
--to=dmoncayo@gmail.com \
--cc=13480@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).