[dolphin] [Bug 420172] New: Searches should not appear as having ended if Baloo has not indexed all files

Henrique bugzilla_noreply at kde.org
Thu Apr 16 23:22:34 BST 2020


https://bugs.kde.org/show_bug.cgi?id=420172

            Bug ID: 420172
           Summary: Searches should not appear as having ended if Baloo
                    has not indexed all files
           Product: dolphin
           Version: unspecified
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: wishlist
          Priority: NOR
         Component: search
          Assignee: dolphin-bugs-null at kde.org
          Reporter: henriquesarmentogoulartaguiar at gmail.com
                CC: kfm-devel at kde.org
  Target Milestone: ---

After struggling against Dolphin and Baloo for a long while, I have recently
started to understand how Baloo works and how to use it to my favour.

However, I still find it rather problematic. A user should not have to learn
how the inner parts of their system is working to use it - rather, they should
not have to worry about them at all.

The main concern I have, which doesn't seem to be addressed anywhere else, is
that when searching for a file, if Baloo does not find it, Dolphin will act as
if the file does not exist. Even if Baloo has not indexed all files, even if it
acknowledges the file exist but hasn't gotten to it. "No items found", or "0
Folders, 0 Files".

That is rather problematic. A user who does not understand that the search
engine may not show existing files will either believe the file doesn't exist,
or will (rightly) think the search function is broken.

What I propose is some manner of indicating Dolphin hasn't "finished" searching
if it is not 100% sure it looked everywhere, and preferably, some way to force
Baloo to finish indexing and searching right then and there.

Or we can just jump ships and stop using Baloo as the default mechanism
(https://bugs.kde.org/show_bug.cgi?id=391677).

I'm not familiar with the way Dolphin or Baloo is coded, so I'm not sure what
is possible. But I hope my feedback is useful in creating a less frustrating,
more user-friendly experience.

-- 
You are receiving this mail because:
You are on the CC list for the bug.



More information about the kfm-devel mailing list