Bug 427087 - setting logic is inconsistent
Summary: setting logic is inconsistent
Status: RESOLVED LATER
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Engine (show other bugs)
Version: unspecified
Platform: Manjaro Linux
: NOR major
Target Milestone: ---
Assignee: Stefan Brüns
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-28 20:35 UTC by Rüdiger
Modified: 2020-10-01 09:37 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rüdiger 2020-09-28 20:35:57 UTC
SUMMARY
Activating the file search in KDE system settings offer these options:
1. Activate file search: yes
--> 1.1 also content indexing
(--> 1.2 index hidden files and folders)
2. Folder specific configuration
you can select for each folder two options
---------> 2.1 not indexed
---------> 2.2 full content indexing

If you activate 1.2 you can select again the same with 2.2.
For what you can select the same option 2 times but you cannot select at all "index file names only"?
And for what can you select "not indexing", if you cannot select any folder for "index file names only"?
If you deactivate 1.1 you still only can select 2.1 "not indexed" and 2.2 "full content indexing" but again not differentiate to "index file names only".

In my opinion you do not need option 1.1 at all. But you need three option under 2. As they should be
---------> 2.1 not indexed
---------> 2.2 full content indexing
---------> 2.3 "index file names only"

This makes baloo search settings not proper usable. This may be a wishlist but for me it is an essential bug because there is no logic in using baloo properly.


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Stefan Brüns 2020-09-28 21:10:45 UTC
Settings are consistent. Whether to do fulltext indexing or file names only is a global option currently.

Everything else is an additional feature.
Comment 2 Rüdiger 2020-10-01 09:37:57 UTC
(In reply to Stefan Brüns from comment #1)
> Settings are consistent. Whether to do fulltext indexing or file names only
> is a global option currently.
> 
> Everything else is an additional feature.

Thanks. But honestly the logic does not really make sense.
What does it mean, if
--> 1.1 also content indexing  ON
---------> 2.2 full content indexing ON?
There is redundancy.
What does it mean, if 
--> 1.1 also content indexing  OFF
---------> 2.2 full content indexing ON?
Will the folder to 2.2 full content indexed or not?

What does it mean, if 
--> 1.1 also content indexing  ON
---------> 2.1 not indexed ON (folder)
Will the folder still be file indexed only?

Actually it would be much simpler and clearer, if there is only one hierarchy level, settings only be made for folder/disks e.g.
- full content indexed
- file indexed 
- not indexed
And if subfolder are different than than rule should be applied from the subfolder.