Re: Interpretation of a space in regexp isearch?

[Bastien]

Chong Yidong <address@hidden> writes:

> Dani Moncayo <address@hidden> writes:
>
>> IMO, that feature is what the user usually wants in an ordinary search
>> (regardless it's incremental or not; even if that search is part of a
>> ordinary replace command).
>>
>> On the other and, in a rexexp search (or regexp search&replace) I
>> think that the common case is the opposite: the user normally doesn't
>> want that feature.
>
> I committed a change to trunk to make non-regexp isearch match multiple
> spaces via search-spaces-regexp.

Great, thanks.

> As for regexp isearch, it seems disruptive to remove the feature now,
> since some some users might have grown to rely on it.  So I left regexp
> isearch alone (i.e. it still does the multiple spaces matching).

I think the behavior in regexp isearch will be less surprising now.
So keeping the two behaviors (in isearch and regexp isearch) in sync
looks okay to me.

> It is now possible to change the variable `search-whitespace-regexp' and
> give it a cons cell value, which specifies different behaviors for
> ordinary and regexp isearch.

Even better!  Thanks for implementing this,

-- 
 Bastien