If it's possible, please do not implement this or implement it as a facultative feature which automatically switches off when there is no Baloo index for the searched place.

It would be good to have an alternative to Baloo semantic search without indexing. So the users that have to switch Baloo off due to the unresolved problems, like https://bugs.kde.org/show_bug.cgi?id=400704 , still can use KDE search capabilities.

Now, Qt5-only version of KFind (Applications 18.12) uses the same metadata engine (KFileMetadata) as Baloo and is as much effective in this sense as Baloo. There is no need for duplication, imho.

This is a quite old feature request and it looks like there is currently no consensus on how/if it should be implemented. Should this get marked as RESOLVED:WONTFIX?

For what is worth I'd prefer for KFind to have zero reliance on Baloo index. I have Baloo disabled in all my systems and I am happy to use KFind as-is.

(In reply to Yuri Chornoivan from comment #1)
> ... or implement it as a
> facultative feature which automatically switches off when there is no Baloo
> index for the searched place ...
Dolphin does this. It knows what Baloo been has configured to index and if you are searching "from" a folder that has not been indexed it falls back to its "there and then" filenamesearch.

Better, perhaps, would be for Dolphin (or filenamesearch) to ask Baloo whether it really has indexed the folder, there being a difference between theory and practice...

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!