unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: sbaugh@janestreet.com, 65347@debbugs.gnu.org
Subject: bug#65347: 29.1; Underscore in query replace prevents case-matching
Date: Sat, 19 Aug 2023 22:14:48 +0300	[thread overview]
Message-ID: <83pm3iyhcn.fsf@gnu.org> (raw)
In-Reply-To: <jwv1qfzf5ji.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sat, 19 Aug 2023 11:51:46 -0400)

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: sbaugh@janestreet.com,  65347@debbugs.gnu.org
> Date: Sat, 19 Aug 2023 11:51:46 -0400
> 
> > And what do you mean by "remembered for the next time", when the only
> > difference is in letter-case?
> 
> When it finds "FOo" and converts it to "Bar" and I change it to "BAr" it
> should remember that mapping such that next time it finds that exact
> same capitalization "FOo" it should use "BAr" as replacement.

Is it really what happens in these cases?  IME, the capitalization
patterns, when they don't fit the heuristic, are inconsistent with one
another, and bumping into one such "non-standard" replacement doesn't
mean all those replacements after it will be necessarily
"non-standard", let alone in the same way.

IOW, I believe the best strategy is to keep replacing using the
default heuristic, and leave it to the user to detect the rare
deviations and fix them with ',' or 'C-r'.





  reply	other threads:[~2023-08-19 19:14 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-16 21:27 bug#65347: 29.1; Underscore in query replace prevents case-matching Spencer Baugh
2023-08-17  7:14 ` Eli Zaretskii
2023-08-17 12:42   ` Spencer Baugh
2023-08-17 13:26     ` Eli Zaretskii
2023-08-18  2:04     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-18  6:04       ` Eli Zaretskii
2023-08-18 16:30         ` Spencer Baugh
2023-08-18 18:15           ` Eli Zaretskii
2023-08-18 18:31             ` Spencer Baugh
2023-08-18 19:06               ` Eli Zaretskii
2023-08-18 19:14                 ` Spencer Baugh
2023-08-18 19:29                   ` Eli Zaretskii
2023-08-18 21:00                     ` Spencer Baugh
2023-08-19  6:00                       ` Eli Zaretskii
2023-08-21  1:13                         ` Richard Stallman
2023-08-18 19:20               ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-19  5:50                 ` Eli Zaretskii
2023-08-19 14:39                   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-19 14:50                     ` Eli Zaretskii
2023-08-19 15:51                       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-19 19:14                         ` Eli Zaretskii [this message]
2023-08-20  0:03                           ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-19 14:52                     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-19 15:01                       ` Eli Zaretskii
2023-08-19 16:02                         ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83pm3iyhcn.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=65347@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=sbaugh@janestreet.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).