Perhaps it doesn't matter, but I'd like to point out that this feature will
need to be turned off for Lisp mode buffers, since in many Lisp systems,
system output contains names (symbols) that are in uppercase, while in the
source files, these names appear in lowercase.
- Richard Harris
-----Original Message-----
From: Didier Verna [SMTP:vernaļ¼ inf.enst.fr]
Sent: Friday, September 25, 1998 9:46 AM
To: Xemacs Patches
Cc: XEmacs beta list
Subject: [PATCH] to improve case management in search routines.
In addition to the bug Hrvoje fixed in isearch, I'd like to propose
the following patch to generalize the behavior of isearch (which is the
Right
One) to other searches as well. The point is that when calling
interactively a
routine that leads to a search (even basic, non-incremetal, non-regexp
ones),
the introduction of an uppercase character in the search srting should
switch
back to case-sensitive search, regardless of the value of case-fold-search
(but still taking search-caps-disable-folding). isearch currently behaves
this
way, but we'd like to see other functions (like zap-to-char) follow this
rule
too.
The following patch generalizes the use of isearch-no-upper-case and
with-caps-disable-folding (moving them away from isearch.el), and corrects
the
behavior of the `zap-*-to-char' functions. I'm likely to modify other
functions along with the same lines in the future as they come to my mind.
One important point: there are 2 interface changes in this patch:
the
routine isearch-no-upper-case-p is moved away from isearch.el in order to
be
used anywhere else, so the isearch- prefixe is removed. The other one is
one
more argument (regexp-flag) to the macro with-caps-disable-folding, which
is
moved away from isearch too. I think we can afford those changes: they
lead to
only 2 other modifications in the core lisp packages, and none of the
packages
I have installed (almost all of them) use those functions.
_this patch must be applied on top of hrvoje's previous one_
(<kigyarb68yb.fsf(a)jagor.srce.hr>)