Re: [RFC] the behavior of search_command
Hrvoje Niksic <hniksic(a)srce.hr> writes:
Although your suggestion makes sense as a user-interface
improvement,
I'm certain that much code depends on case-fold-search doing what it
says it does, no matter what the search string is. For example:
(let ((case-fold-search nil))
(re-search-for "^Content-Length:")
..)
In this particular case, my suggestion doesn't change anything. What I
suggested is check the search string ONLY when case-fold-search is non nil,
which means that we're not supposed to care about the case.
Checking whether the function is called interactively would be likely
to
fail when a higher-level function non-interactively calls a lower-level
function to search for a user-specified string.
The second solution I proposed was exactly to change the behavior of
very high level functions only, like zap-to-char.
The only good solution I see is to explicitly request this behaviour
in higher-level Lisp code.
See above.
Note that the `with-caps-disable-folding' macro exists for this
very
purpose.
I didn't know about this one.
--
Didier, typing this not far away from you :-)