Pre-KF5 versions of KRunner would pull up a file when one typed in a query that was a substring of the filename. KRunner now instead prioritizes all occurances of the query inside of baloo-indexed documents rather than displaying on top the match from the file name. I've shown an example here: http://wstaw.org/m/2015/11/23/krunnerbug.png It turns out that I indeed have a file named Lamb_Sir_Horace_Hydrodynamics.pdf under a subdirectory of $HOME -- however, the results I see are mostly matches for words inside the documents. Reproducible: Always Steps to Reproduce: 1. Fire up KRunner 2. Type a query string that matches a document's file name, but is also present in many of the other documents indexed by baloo 3. The file-name match is not prioritized over a body indexed-text match. Actual Results: The file-name match is drowned amidst full-text matches Expected Results: It would be much preferable to have the document where there is a filename match (or more generally metadata match) on the top of the list of matches. Question: It might be even better if directory search is provided by a different module?
It would be useful if the current "document" runner had an option to search for filenames and perhaps filenames only. If searching both contents and filenames it could prioritize filenames over contents, or provide an option for setting priority. Otherwise, a separate krunner to search for filenames would be very useful, but I think it doesn't make sense to have a separate runner for that when the functionality should be put in the current "document" runner. I guess this is a wish rather than bug, but given that the functionality existed KDE4, it looks like a regression. PS. the title of this report does not exactly make it easy to find!
Search by content annoying in a lot times, because the result list is so long that it's difficult to find what wanted.
*** This bug has been confirmed by popular vote. ***
Option 1: In KRunner, use "filename:foo" Option 2: In Dolphin -> "Find ...", select "Filename"
Since searching for a file by its name is a common use case, could the keyword 'filename:' be shortened? Say, to 'f:'?
Or "file:foo"
As far as I can tell Baloo does not provide an option to limit a query nor information in the return results whether the match occurs in the file name or file contents, so such an option would have to be added to Baloo before KRunner could make use of it. Even better would be if filtering out content matches altogether weren't necessary because this relevance would be adequately reflected in the sorting, which Baloo currently does not seem to do.