On 3/8/07, Philip Ganchev <[EMAIL PROTECTED]> wrote: > On 3/7/07, Axel Liljencrantz <[EMAIL PROTECTED]> wrote: > > I haven't been very active in this discussion because of various real > > life issues, including the fact that I will present my licenthiate > > thesis tomorrow, but I am reading all entries with interest. > > I hope it went well!
It did. Thanks! > > [...] > > If I were to summarize the above discussion, it would read something like > > this: > [...] > > * It might be acceptable to only support case insensitive completions > > on non-wildcarded strings for now. > > The only argument I found for treating wildcards specially was: > > On 3/3/07, Greg K <[EMAIL PROTECTED]> wrote: > > [...] users want case insensitive completion in simple and quick > > cases. In more complicated situations (where they are taking the trouble > > to use wildcards), case insensitivity probably ought to be indicated by > > the search expression. > > I suppose the search expression is the string to be completed. I > don't understand why it's a good idea to change the case of a string > without wildcards but not one with wildcards. Presumably, if you are > using wildcards you are less certain about the command than if you are > not. > > It is an interesting idea to be able to say that you don't want the > case to be changed. But using wildcards is not a good way to do this, > because they make the expression more general, not more specific. One > way to do it is to do a case-sensitive search if the string includes > any uppercase letters. So ".xres" would complete to ".Xresources", > but ".xRes" and ".XRes" would not. But this does not let you specify > exact case for an all-lowercase string. Instead, it may be better to > use a quasi-mode, like Shift+Tab if you want case-exact completion. My bad, I was unclear. I only meant that it might be acceptable to to so temporarily, but that long term, the stated goal should be to provide 100 % consistent casing behaviour. > > > So my preference would to indicate the desired case sensitivity > > explicitly in the wildcard string and do the expansion based on that. In > > the absence of some way to do that, I actually think that your option: > > > > >* Do not provide any case insensitive completions for string > > > containing expansion characters like wildcards. This is inconsistent > > > and limits the usability of case insensitive completions. > > > > would actually be pretty workable from an end user standpoint. > [...] > > I agree that it would be workable, but not preferable. > > Incidentally, will history search use the same rules about case? Very good questions. Hadn't thought about it. Makes sense to me. Opinions? -- Axel ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Fish-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fish-users
