From: Dani Moncayo <dmoncayo@gmail.com>
To: Bastien <bzg@altern.org>
Cc: Nicolas Richard <theonewiththeevillook@yahoo.fr>,
Dan Jacobson <jidanni@jidanni.org>,
16546@debbugs.gnu.org
Subject: bug#16546: C-s vs. whitespace highlighting
Date: Mon, 27 Jan 2014 08:50:52 +0100 [thread overview]
Message-ID: <CAH8Pv0gqkUnsnjzY-HqGM-RfeuNaxdT-Ub5hO8W9L0KCV2TdJA@mail.gmail.com> (raw)
In-Reply-To: <87lhy2idcs.fsf@bzg.ath.cx>
>> When I specifically add two spaces to my search string, it usually means
>> that, at that point, I want at least two spaces. If I compare to the
>> similar feature of case folding, that one is deactivated when there is
>> an explicit capital letter in the search string. OTOH, the cases where I
>> actually want to match multiple spaces are rare enough.
>
> Yes, good idea. I also think search for two whitespace chars in a row
> should temporary toggle `search-whitespace-regexp' to nil.
IMO, that behavior would make sense only when the whitespace chars are
entered interactively (i.e. typed on the keyboard), because if the
search string comes from another place (copy&paste, grabbed from the
buffer, ...), I don't think it would be a good idea to temporarily set
`search-whitespace-regexp' to nil. And BTW, that reasoning applies
equally to case-fold-search.
IOW, if I copy some text "foo<any-whitespace>bar" from one place and
then go to Emacs and do "C-s C-y", I definitely want a "lax" search
wrt whitespace.
At least, that behavior should be configurable, IMO.
--
Dani Moncayo
next prev parent reply other threads:[~2014-01-27 7:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-25 9:49 bug#16546: C-s vs. whitespace highlighting jidanni
2014-01-25 13:46 ` Bastien
2014-01-25 14:17 ` Dani Moncayo
2014-01-26 21:46 ` Nicolas Richard
2014-01-26 22:32 ` Bastien
2014-01-27 2:16 ` Stefan Monnier
2014-01-27 7:09 ` Bastien
2014-01-27 7:50 ` Dani Moncayo [this message]
2014-01-27 8:21 ` martin rudalics
2014-01-27 8:35 ` Dani Moncayo
2014-01-27 9:21 ` Juri Linkov
2014-01-27 9:55 ` Dani Moncayo
2014-01-28 7:30 ` Juri Linkov
2014-01-25 14:23 ` jidanni
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAH8Pv0gqkUnsnjzY-HqGM-RfeuNaxdT-Ub5hO8W9L0KCV2TdJA@mail.gmail.com \
--to=dmoncayo@gmail.com \
--cc=16546@debbugs.gnu.org \
--cc=bzg@altern.org \
--cc=jidanni@jidanni.org \
--cc=theonewiththeevillook@yahoo.fr \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.