From: Drew Adams <drew.adams@oracle.com>
To: rms@gnu.org, Eli Zaretskii <eliz@gnu.org>
Cc: 22494@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#22494: still can't search for two spaces
Date: Sat, 30 Jan 2016 14:28:26 -0800 (PST) [thread overview]
Message-ID: <54a07b7d-1fbd-4ed1-a8a0-e22eb5787c97@default> (raw)
In-Reply-To: <<E1aPdiw-0001yi-W4@fencepost.gnu.org>>
> > > I still can't search for two spaces with C-s SPC SPC.
> > > It still just sits on the first match for single space.
>
> > Crystal ball says you didn't read the manual, which explains that you
> > need to type M-s SPC after C-s to get what you want (which is literal
> > space matching).
>
> This is a bug. When the user types SPC SPC in a search string,
> person clearly wants to search for two spaces. It should do that.
+1
If lax-whitespace matching is currently turned on, typing
multiple whitespace chars contiguously could turn it off.
But in that case a message should let the user know that this
change has occurred.
And then what if the user made a mistake typing that second SPC
char - i.e., didn't really mean to search literally for multiple
whitespace chars? It won't be enough to just delete the second
SPC char (but the user might try that).
Perhaps the message that lax whitespace matching has been switched
to literal should also mention the key sequence for toggling
back to lax matching.
next parent reply other threads:[~2016-01-30 22:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2016-01-30 22:47 ` bug#22494: still can't search for two spaces Marcin Borkowski
2016-01-31 0:02 ` Drew Adams
2016-01-31 20:31 ` Richard Stallman
2016-01-31 0:08 ` Juri Linkov
[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 ` 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
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
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=54a07b7d-1fbd-4ed1-a8a0-e22eb5787c97@default \
--to=drew.adams@oracle.com \
--cc=22494@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jidanni@jidanni.org \
--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).