From: Artur Malabarba <bruce.connor.am@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 21192@debbugs.gnu.org, Dima Kogan <dima@secretsauce.net>
Subject: bug#21192: 25.0.50; search-replace of spaces erroneously touches newlines
Date: Wed, 5 Aug 2015 18:49:46 +0100 [thread overview]
Message-ID: <CAAdUY-+F1OBqJ=H4Hww9nHZaEFof9gx4m2V=KZ2UP=DgZuCFQw@mail.gmail.com> (raw)
In-Reply-To: <8337zxu5q1.fsf@gnu.org>
2015-08-05 16:15 GMT+01:00 Eli Zaretskii <eliz@gnu.org>:
>> From: Dima Kogan <dima@secretsauce.net>
>> Date: Wed, 05 Aug 2015 03:10:27 -0700
>> Cc: 21192@debbugs.gnu.org
>>
>> Artur Malabarba <bruce.connor.am@gmail.com> 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.
next prev parent reply other threads:[~2015-08-05 17:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 8:29 bug#21192: 25.0.50; search-replace of spaces erroneously touches newlines Dima Kogan
2015-08-05 9:40 ` Artur Malabarba
2015-08-05 10:10 ` Dima Kogan
2015-08-05 15:15 ` Eli Zaretskii
2015-08-05 17:49 ` Artur Malabarba [this message]
2015-08-05 18:17 ` Artur Malabarba
2015-08-05 20:46 ` Dima Kogan
2015-08-06 9:15 ` Artur Malabarba
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='CAAdUY-+F1OBqJ=H4Hww9nHZaEFof9gx4m2V=KZ2UP=DgZuCFQw@mail.gmail.com' \
--to=bruce.connor.am@gmail.com \
--cc=21192@debbugs.gnu.org \
--cc=dima@secretsauce.net \
--cc=eliz@gnu.org \
/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.