unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: Nicolas Richard <theonewiththeevillook@yahoo.fr>
Cc: jidanni@jidanni.org, 16546@debbugs.gnu.org
Subject: bug#16546: C-s vs. whitespace highlighting
Date: Sun, 26 Jan 2014 23:32:03 +0100	[thread overview]
Message-ID: <87lhy2idcs.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87bnyyifgr.fsf@yahoo.fr> (Nicolas Richard's message of "Sun, 26 Jan 2014 22:46:28 +0100")

Hi Nicolas,

Nicolas Richard <theonewiththeevillook@yahoo.fr> writes:

> Bastien <bzg@altern.org> writes:
>> I think the default is good because the need to match "a  word" with
>> "C-s a word" is more likely than the need not to match "a word" with
>> "C-s a  word".
>
> 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.

-- 
 Bastien





  reply	other threads:[~2014-01-26 22:32 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 [this message]
2014-01-27  2:16       ` Stefan Monnier
2014-01-27  7:09         ` Bastien
2014-01-27  7:50       ` Dani Moncayo
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

  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=87lhy2idcs.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --cc=16546@debbugs.gnu.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 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).