On 3/1/07, Martin Bähr <[EMAIL PROTECTED]> wrote:
> On Fri, Mar 02, 2007 at 01:04:54AM +0200, Beni Cherniavsky wrote:
> > 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 alt
On Fri, Mar 02, 2007 at 01:04:54AM +0200, Beni Cherniavsky wrote:
> 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.
even if there is only a single com
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.
I have been experimenting a bit with implementing case insensitive tab
completions. There is a working implementation in the darcs repo, but
it is not without corner cases.
My current thoughts on the subject:
I like the idea of using case insensitive completions as a fallback
when case sensitive
