From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>, Kaushal <kaushal.modi@gmail.com>
Cc: 20687@debbugs.gnu.org
Subject: bug#20687: 25.0.50; `perform-replace' should invoke a key that you have bound in `query-replace-map'
Date: Tue, 2 Jun 2015 15:50:51 -0700 (PDT) [thread overview]
Message-ID: <f0a2bf44-165c-4125-8985-87fb17e31087@default> (raw)
In-Reply-To: <87zj4hsr90.fsf_-_@mail.linkov.net>
> > + ;; Show whether `case-fold-search' is `t' or `nil'
> > + (if case-fold-search "[case] " "[CaSe] ")
>
> Maybe we should use the same message about case-folding like in
> isearch?
The msg should somehow indicate that what is involved here is (only)
case-sensitivity wrt FROM (i.e., wrt search, not replacement). Not
sure what the best way to do that would be.
IOW, there is more than one use of case sensitivity here, unlike
the case for search. There is what `case-fold-search' controls (the
search), and there is what `case-replace' controls (the replacement).
And then there is what happens for the replacement according to the
case of FROM.
---
BTW, we might consider binding a key to toggle case sensitivity for
search as part of this bug fix (i.e., not just fixing `perform-replace'
so it respects keys that user might bind). In that case, maybe the
same key we use in Isearch (`M-c') would be a good choice.
---
BTW2, I think that Emacs manual node `Replacement and Case' is confusing.
The first three paragraphs (2/3 of the node), for instance:
If the first argument of a replace command is all lower case, the
command ignores case while searching for occurrences to
replace--provided `case-fold-search' is non-`nil'. If
`case-fold-search' is set to `nil', case is always significant in all
searches.
An upper-case letter anywhere in the incremental search string makes
the search case-sensitive. Thus, searching for `Foo' does not find
`foo' or `FOO'. This applies to regular expression search as well as
to string search. The effect ceases if you delete the upper-case
letter from the search string.
If you set the variable `case-fold-search' to `nil', then all
letters must match exactly, including case. This is a per-buffer
variable; altering the variable normally affects only the current
buffer, unless you change its default value. *Note Locals::. This
variable applies to nonincremental searches also, including those
performed by the replace commands (*note Replace::) and the minibuffer
history matching commands (*note Minibuffer History::).
These paragraphs really say only that the search part of replace commands
acts normally: `case-fold-search' governs. They should be removed or
changed to say just that. Leaving them as they are just confuses readers, IMO.
next prev parent reply other threads:[~2015-06-02 22:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 21:12 bug#20687: 25.0.50; `perform-replace' should invoke a key that you have bound in `query-replace-map' Drew Adams
2015-06-01 20:53 ` Juri Linkov
2015-06-01 21:11 ` Drew Adams
2015-06-02 22:01 ` Juri Linkov
2015-06-02 22:12 ` Drew Adams
2020-09-17 18:11 ` Lars Ingebrigtsen
2015-06-02 13:08 ` Kaushal
2015-06-02 22:02 ` Juri Linkov
2015-06-02 22:50 ` Drew Adams [this message]
2015-06-03 3:35 ` Kaushal
2015-06-03 4:39 ` Drew Adams
2015-06-03 5:10 ` Kaushal
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=f0a2bf44-165c-4125-8985-87fb17e31087@default \
--to=drew.adams@oracle.com \
--cc=20687@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=kaushal.modi@gmail.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).