From: John Wiegley <jwiegley@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: 22494@debbugs.gnu.org, mbork@mbork.pl, rms@gnu.org, jidanni@jidanni.org
Subject: bug#22494: still can't search for two spaces
Date: Tue, 02 Feb 2016 22:45:41 -0800 [thread overview]
Message-ID: <m2bn7ymgve.fsf@newartisans.com> (raw)
In-Reply-To: <6281db1e-d974-4cdc-b111-3e9097ae89db@default> (Drew Adams's message of "Sun, 31 Jan 2016 13:29:26 -0800 (PST)")
>>>>> Drew Adams <drew.adams@oracle.com> writes:
> Heeding what is in the search string means nothing - or anything.
I don't know why you're saying this Drew.
If the user types something into the search string, and exactly that something
is present in the buffer, Emacs should locate it before any "lax" variant.
This means that type "nD" where nD exists, should find nD. Typing " " where
two spaces exist, should find the two spaces.
Whether or not lax whitespace matching should be the default is an entirely
separate matter. I rather like the lax matching, so long as my use of two
spaces in a search string does not mean that I can't find two spaces.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
next prev parent reply other threads:[~2016-02-03 6:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<<87h9hvshi3.fsf@jidanni.org>
[not found] ` <<<E1aPdiw-0001yi-W4@fencepost.gnu.org>
[not found] ` <<54a07b7d-1fbd-4ed1-a8a0-e22eb5787c97@default>
[not found] ` <<871t8yit11.fsf@mbork.pl>
[not found] ` <<77b5b6df-4889-4142-a04d-526dd94c3a48@default>
[not found] ` <<E1aPyeg-0003QJ-B5@fencepost.gnu.org>
2016-01-31 21:29 ` bug#22494: still can't search for two spaces Drew Adams
2016-02-01 11:01 ` Richard Stallman
2016-02-01 11:20 ` Andreas Schwab
2016-02-01 14:15 ` Dani Moncayo
2016-02-03 6:45 ` John Wiegley [this message]
2016-02-03 14:57 ` Drew Adams
2016-02-03 18:56 ` John Wiegley
2016-02-03 19:08 ` Drew Adams
2016-02-03 15:28 ` Eli Zaretskii
2016-02-03 15:44 ` Nicolas Richard
[not found] <<87h9hvshi3.fsf@jidanni.org>
[not found] ` <<8337tfy0p3.fsf@gnu.org>
[not found] ` <<E1aPdiw-0001yi-W4@fencepost.gnu.org>
2016-01-30 22:28 ` Drew Adams
2016-01-30 22:47 ` Marcin Borkowski
2016-01-31 0:02 ` Drew Adams
2016-01-31 20:31 ` Richard Stallman
2016-01-31 0:08 ` Juri Linkov
2016-01-30 6:34 積丹尼 Dan Jacobson
2016-01-30 7:40 ` Eli Zaretskii
2016-01-30 22:10 ` Richard Stallman
2016-01-31 5:39 ` John Wiegley
2016-01-31 16:08 ` Drew Adams
2016-02-01 0:13 ` 積丹尼 Dan Jacobson
2016-02-01 1:57 ` Drew Adams
2016-02-01 3:10 ` 積丹尼 Dan Jacobson
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=m2bn7ymgve.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=22494@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=jidanni@jidanni.org \
--cc=johnw@gnu.org \
--cc=mbork@mbork.pl \
--cc=rms@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).