Re: completing-read doesn't require exact match when completion-ignore-case is set

[Stefan]

>> Yes, this is legitimate.  When completion-ignore-case is t,
>> `fooa' and `fooA' do match.

> Right -- but surely

>   M-: (read-buffer "Buffer: " nil t)

> shouldn't be able to return the name of a non-existing buffer?  Is
> this then a deficiency in the implementation of read-buffer, and the
> way it uses completing-read?

I think the problem is that the name `completion-ignore-case' seems to imply
that it only affects completion whereas it also affects the accepted values
of `require-match' is set.

I think what should happen is that if `completion-ignore-case' is set and
`require-match' is also set, completing-read should automatically fix the
case before returning (which IIRC already happens if you hit TAB before
RET).

        Stefan