[RFC] the behavior of search_command

Several interactive search functions use the internal search_command function. This is *the* function that decides whether to be case-sensitive, according to the value of case-fold-search. In the case where case-fold-search is non nil (ignore case), I find the behavior not optimal. Basically (at least in the interactive case), I'd like to be able to type uppercase characters in order to specify that I want actually a case-sensitive search, just for this time, regardless of the value of case-fold-search. What this means is that when case-fold-search is non nil, we should scan the search string for uppercase characters, in order to decide whether to be really case-insensitive or not. There are two ways to achieve this: we can modify search_command (I have a patch ready for this), or we can modify each concerned lisp function. The point is that I don't know if there are non-interactive cases that could be fucked up with this new feature. If not, we'd better patch search_command directly. If yes, then it's preferable to modify the lisp functions, and check if we're calling them interactively. Or maybe not, if we use (downcase ...) to ensure we'll match everything ... RFC. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 73 46 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19