bug#38458: 27.0.50; case-insensitive substring completion

[Stephen Berman <stephen.berman@gmx.net>]

On Tue, 03 Dec 2019 09:47:18 -0500 Stefan Monnier <monnier@iro.umontreal.ca> wrote:

>> If those changes caused this issue, then I think there was already a
>> bug in the substring completion style, which was just exposed by those
>> changes.
>
> Indeed.  I just pushed a fix to `master`.  Thank you.

FTR, I confirm that fixes the issue I reported, thanks.

While I was testing cases for the bug report, I noticed that,
independent of case, the placement of point in substring completion is
sometimes suboptimal.  E.g. if there two files (or buffers) file1test
and file2test and you enter `fi TAB' then it completes to `file' with
point after the `e', which is fine for further input; but if you enter
`te TAB' then it completes to `test' with point after the second `t', so
you have to move point to complete the name.  It would be nice if in
such cases point were placed at the start rather than the end of the
partial match.  Should I make a feature request?

Steve Berman