Created attachment 162146 [details] Search doesn't return items based on substring comparing The comparing is working only if the searched word is found between two separators like '.', space or '_', but it doesn't work if the word is concatenated to other non separator characters. See attached image for more info.
Created attachment 162148 [details] Wrong result for "*data"
Does the same thing happen in the command-line `baloosearch` program?
(In reply to Nate Graham from comment #2) > Does the same thing happen in the command-line `baloosearch` program? Yes, the same results are returned by "baloosearch" command.
If you using the Baloo index, then this is not supported as per Bug 452628 (and also Bug 453291) Dolphin's "There and Then" search - that it falls back to if Baloo is not available - does however manage wildcards.
(In reply to tagwerk19 from comment #4) > If you using the Baloo index, then this is not supported as per Bug 452628 > (and also Bug 453291) > > Dolphin's "There and Then" search - that it falls back to if Baloo is not > available - does however manage wildcards. If I disable Baloo I get much more weird results: Consider the following files inside a folder : lessdata.txt godata_test.txt datatest.txt data.test.txt data_test.txt - Searching for "*data*" returns nothing - Searching "data" returns all files - Searching "data*" returns all files
(In reply to medin from comment #5) > - Searching for "*data*" returns nothing > - Searching "data" returns all files > - Searching "data*" returns all files Apologies, you are quite right. The filenamesearch copes with substrings (searches for "ata" and "ess" work for me) but not with arbitrary wildcards (searches for "*ata*", "*ess*" don't).