Search doesn't prioritize closest match

[CoenraadS]

I am typing 'proje' to get into my projects folder, which I would expect to be closest match

[IgorKrupenja]

This is due to matching being set to *str* instead of str* starting from 1.3.2. I think the best option solution would be to allow users to configure the desired behaviour in the settings file. @mherrmann, for some more ideas with usage examples, please also see my comment at #512 (comment).

[mherrmann]

That's exactly the case I was worried about when implementing #512. If str* is the default, then you can always type in the leading * for a substring (rather than a prefix) match. But not the other way around.

I'm somewhat weary of configuration options, because most users will never realize they're there. The default behavior needs to be "good enough".

@krupenja can't you fix your "dropbox" example by not displaying hidden files? This should get rid of the .dropbox... folders, shouldn't it?

I'll think about this a little.

[rmgk]

In case you did not consider this: it seems possible to do both for this use case, filter by sub string, but move the cursor to the first prefix match.
At least for my use cases, it seems that prefix match is only preferable for element selection, not filtering.

[mherrmann]

That's a very good idea @rmgk. I implemented it this way now. Will go live with fman 1.3.7.

[mherrmann]

Implemented in fman 1.3.7.