Autocomplete of titles messes with letter case

When typing in the search/create bar, nvUltra matches against existing note titles. While doing so the typed text is replaced by the matched text which is of course identical – except for any differences in letter case. As soon as the typed text no longer matches any existing notes, the whole title is displayed exactly as typed again.

To me this is confusing and sometimes makes me struggle to create a note with the title and case I want. In nvALT, the search/create bar always displays the typed text, even if the currently matched note uses different case for some letters.

Example:

Given an existing note "foo bar.md", and that I want to create the note "FOO.md", I type "FOO". nvUltra matches against the existing file and displays "foo[ bar.md]".

I don't want to open the existing file and I have already typed the complete title I want, so I delete the suggestion using backspace. nvUltra then displays "foo", which still is not what I typed.

If I now hit enter, a file named "foo.md" will be created, which is not what I want. It's not obvious how to proceed instead, so maybe I type a space, causing the autosuggestion to be displayed again ...

What I need to do instead is type a suffix that (hopefully) doesn't match any existing file, like "x". nvUltra will then display "FOOx" and if I erase the "x" the title will stay as I typed it, and I can hit enter to create my file.

My example is contrived, but my confusion is real. Even if the new title is not a prefix of an existing file, but will eventually display correctly when I've typed the complete title, my reflex is to go back and fix the word that vUltra seemingly messed up right when it happens. (Which won't work since the word will still match the same note, so the same thing will happen again.)

I'd much prefer the behavior of nvALT, where the search bar displays what I typed. (In the example above nvALT would have displayed "FOO[ bar]" when first matching the existing file.)

Thanks

/Daniel