Re: case-sensitivity: bug or feature in query-replace?
Stef Epardaud <stef(a)lunatech.com> wrote:
well, it deduces case-sensitivity from uppercase characters in the
FROM,
but what do you think the user expects when he wants to replace 'blabla'
with 'blaBla', really ?
The whole point is that you can't tell. Maybe Joe wants lowercase
`blabla' to be replaced (lie I do most of the time), or maybe not. You just
can't tell. However, there's a big difference in finding an uppercase letter
in FROM because there's no reason to type uppercase letters in there, unless
you actually want case sensitivity. There, you *can* tell[1].
i mean, if i don't put any uppercase letters in FROM but
specifically
put some in TO, does it not mean i _want_ case-sensitivity ?
Well, no. If I want to convert all instances of "emacs" and
"Emacs" to
"EMACS", sure I don't want case sensitivity. I'm happy to do a `replace
"emacs" with "EMACS"' without case sensitivity.
BTW, the real problem is that case-fold-search is an abomination
though. We have to cope with it.
Footnotes:
[1] Kyle objected once that this is not always the case, like if you're
pasting an X selection.
--
/ / _ _ Didier Verna http://www.inf.enst.fr/~verna/
- / / - / / /_/ / ENST, INFRES C201.1 mailto:vernaļ¼ inf.enst.fr
/_/ / /_/ / /__ / 46 rue Barrault Tel. +33 (1) 45 81 73 46
75013 Paris, France Fax. +33 (1) 45 81 31 19