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

            Bug ID: 463830
           Summary: Summary: Differences between Dolphin's filenamesearch
                    and baloosearch
    Classification: Frameworks and Libraries
           Product: frameworks-baloo
           Version: unspecified
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: baloo-bugs-n...@kde.org
          Reporter: tagwer...@innerjoin.org
  Target Milestone: ---

SUMMARY:

    A review of the differences between Dolphin's filenamesearch and
baloosearch -
    surprises and traps for the unwary.

BASE ISSUE:

    Dolphin search asks baloo when it thinks baloo has indexed the folders. If
Dolphin
    thinks baloo has not indexed the files, it will fall back to using it's own
"there
    and then" search.

    The two searches behave differently

    You can see whether Dolphin will ask baloo or doing a "there and then"
search
    by looking at the search prompt. If you do a Ctrl-F to get the prompt and
it
    looks like this:

        https://bugsfiles.kde.org/attachment.cgi?id=137170

    then you will be doing the "there and then" (filenamesearch) search. If
however
    you see extra search options as here:

        https://bugsfiles.kde.org/attachment.cgi?id=137169

    then Dolphin knows it can ask baloo for its search results (baloosearch)

    As always this is a "best efforts" summary, no doubt there's something I've
missed,
    quite likely something I've got wrong. The behaviours have been checked on
Neon
    Testing and Fedora 36.

TERMINOLOGY:

    Beware, there are twisty passages all alike...

    Dolphin can call baloo or do its own "there and then" search, the code it
uses to
    do these are "baloosearch" and "filenamesearch". The search prompts you get
    are dependent on which code Dolphin has decided to use.

    Separately, Dolphin gives you options for searching for filenames or
content. A
    "filename" search and the filenamesearch code are not related and a
"content"
    search does not necessarily depend on baloo. Dolphin tries to provide
search
    functions irrespective of whether baloo is enabled.

    There is also a command line "baloosearch", useful for troubleshooting.

OBSERVED RESULTS:

    These are split up into "traps for the unwary" for Dolphin's "there and
then" search,
    listed under Comment 1, and for Dolphin's "baloo" searches, listed under
Comment 2

WISHED FOR RESULTS:

    Ideally, Dolphin should give the same results (as far as is possible)
irrespective of
    whether it is asking baloo or doing its own search.

    Dolphin should ask baloo whether it has indexed a folder, rather than
assume it has 
    (or hasn't). If baloo has indexed a folder, Dolphin should query baloo in
preference
    to doing its own "there and then" search.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to