Search orders results confusingly

[iFreilicht]

See this example:

I am searching for "optionals", and there is lib.optionals that matches this search exactly, but it is not the first result or even on the first page.

[hsjobeki]

I guess we need to optimize the search for typical nix user expectations.

I think "lib.optionals" is seen by the search as one word if you search for "optionals" the levenstein distance to "optional" is much closer than to "lib.optionals". We need to change the default search indexing and introduce word splitting for the tokenizer at the (.) dot and also apply some weights for the last part of the string.

So lib.optionals is tokenized into [lib optionals] with a higher weight on "optionals".