[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#21192: 25.0.50; search-replace of spaces erroneously touches newline
bug#21192: 25.0.50; search-replace of spaces erroneously touches newlines
Wed, 5 Aug 2015 18:49:46 +0100
2015-08-05 16:15 GMT+01:00 Eli Zaretskii <address@hidden>:
>> From: Dima Kogan <address@hidden>
>> Date: Wed, 05 Aug 2015 03:10:27 -0700
>> Cc: address@hidden
>> Artur Malabarba <address@hidden> writes:
>> > Is your replace-regexp-lax-whitespace variable non-nil, by any chance?
>> It is nil. This issue is from 'emacs -Q'
Yes, of course, you said that. :-) Sorry
> (?\s "\t" "\r" "\n"))) <<<<<<<<<<<<<<<<<<<<<<<<<
> I think we should remove this, since replace-regexp-lax-whitespace
> already provides the same feature, and it's confusing to have that
> variable set to nil and still see such "lax" matches.
Yes. That line is from when `character-fold-to-regexp' didn't do lax
matching. Now it's definitely unnecessary.
> 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.