From: Eli Zaretskii <eliz@gnu.org>
To: bruce.connor.am@gmail.com
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, 05 Aug 2015 18:15:18 +0300 [thread overview]
Message-ID: <8337zxu5q1.fsf@gnu.org> (raw)
In-Reply-To: <87614u6o6k.fsf@secretsauce.net>
> 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 reproducible from 'emacs -Q'
Artur, this happens because we are "folding" newline with whitespace:
;; Add some manual entries.
(dolist (it '((?\" """ "“" "”" "”" "„" "⹂" "〞" "‟" "‟" "❞" "❝" "❠" "“" "„" "〝" "〟" "🙷" "🙶" "🙸" "«" "»")
(?' "❟" "❛" "❜" "‘" "’" "‚" "‛" "‚" "" "❮" "❯" "‹" "›")
(?` "❛" "‘" "‛" "" "❮" "‹")
(?\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.
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 ³.
next prev parent reply other threads:[~2015-08-05 15:15 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 [this message]
2015-08-05 17:49 ` Artur Malabarba
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=8337zxu5q1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=21192@debbugs.gnu.org \
--cc=bruce.connor.am@gmail.com \
--cc=dima@secretsauce.net \
/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.