Subject: Re: bug#21192: 25.0.50; search-replace of spaces erroneously touches newlines

From: Artur Malabarba <[email-masked]>
Date: Wed, 5 Aug 2015 19:17:47 +0100

>> Regardless, I think replace commands should start with character
>> folding off, as I don't think most users will want that by default,
>> especially since we don't perform the reverse transformation when
>> replacing, and so, say, ² is replaced with 3, not with ³.
>
> Sure, I can move it to a variable.

It was already a variable, so I've defaulted it to nil now.

Dima, could you check if this solves your problem?