On 3/2/07, Axel Liljencrantz <[EMAIL PROTECTED]> wrote: > The question that remains is if casing of the original string should > be updated to match the completion. In some cases, this is needed for > case insensitive completions to make sense. Take file and variable > name completion for example. But on the other hand, changing the case > of the string on the commandline is intrusive, and in the general case > it is _really_ hard. There can be more than one way to change the > casing of a token to get a meaningful result. If the user is trying to > complete the string 'echo *aB*c' in a dirtectory containing the files > 'dabdcd' and 'aABdcd', it is not well defined if the replacement > string should be '*AB*cd' or '*ab*cd'.
In cases when there is no single completion that will cover all cases, I as a user would expect the competing options (e.g. '*AB*cd' and '*ab*cd') to be presented as alternative completions. I don't currently see a better interface for choosing one of the options than going back and changing the case of all relevant letters until there is a completion that doesn't require case changing. -- Beni Cherniavsky <[EMAIL PROTECTED]> (I read email only on weekends) ------------------------------------------------------------------------- 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
