From: Drew Adams <drew.adams@oracle.com>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: 22494@debbugs.gnu.org, rms@gnu.org, jidanni@jidanni.org
Subject: bug#22494: still can't search for two spaces
Date: Sat, 30 Jan 2016 16:02:29 -0800 (PST) [thread overview]
Message-ID: <77b5b6df-4889-4142-a04d-526dd94c3a48@default> (raw)
In-Reply-To: <871t8yit11.fsf@mbork.pl>
> >> > > 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
>
> +1
>
> > 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).
>
> Why couldn't it be enough?
It's not a clear indication that the user wants to return to
lax whitespace matching. What if s?he deleted the second SPC
and typed a TAB or other whitespace char? Or typed a SPC char
again? Would you toggle back again?
More than one whitespace char in a row might be sufficient cause
to switch to literal whitespace matching, but it's not clear that
a single such char is sufficient cause to switch to lax matching.
I'd propose a clear message indicating that Emacs has guessed,
because you typed more than one whitespace char in a row, that
you really want literal whitespace char matching, and so it has
switched to that mode. And at the same time indicate that you
can toggle the whitespace-matching behavior using `M-s SPC'.
That should be clear enough, I would think.
next prev parent reply other threads:[~2016-01-31 0:02 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 ` bug#22494: still can't search for two spaces Drew Adams
2016-01-30 22:47 ` Marcin Borkowski
2016-01-31 0:02 ` Drew Adams [this message]
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=77b5b6df-4889-4142-a04d-526dd94c3a48@default \
--to=drew.adams@oracle.com \
--cc=22494@debbugs.gnu.org \
--cc=jidanni@jidanni.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).