@bjc, when you click on the Search field, there’s a “Usage” links that popups where you can read about what’s supported or not. Have you tried clicking on this link?
I think the issue is that Joplin doesn’t do a partial match with an asterisk (*). In your example you had types “tes” and nothing showed up until you completed by typing “test”. I think @bjc would like matches for “test” to show up after typing “tes” (equivalent of typing “tes*”).
@laurent, If I made a pull request for a setting that would automatically append an * to searches would you accept it? I think the searching is fast enough that most users would benefit from this, and those that don’t would simply be able to turn it off.
This is problematic. What if I only wanted notes that included the word tes? If you were to add an asterisk by default, this would no longer be possible.
Unless we make sure that all results with the word tes are really the first ones in the result. Are they?
I think do to the sorting whole matches should usually rank higher (I quick test confirmed this). But I see your point, I wonder if there is an elegant solution to only allow this on typeahead, but after a brief delay you would only get exact matches. I’ll think about it.
Yes I’d like if we could get rid of the asterisk, but we’d need to do so without losing control of the search results.
Currently the query format follows closely FTS4, but perhaps we can have a more user friendly format, then transform it to FTS4 before sending it to Sqlite.