Bug 384963 - baloo first run directive explained opposite
Summary: baloo first run directive explained opposite
Status: RESOLVED UNMAINTAINED
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Pinak Ahuja
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-22 16:35 UTC by Hamidreza Jafari
Modified: 2018-07-18 01:08 UTC (History)
0 users

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Hamidreza Jafari 2017-09-22 16:35:02 UTC 
Baloo help file (link below) mentions that after deleting the index database you should set first run=false in the configuration file. That forces an automatic update again or on startup. It should be the other way around: set it true to indicate it is a first run.

Could even be stated more readable in the conf file: this is first run: true [or false]

https://community.kde.org/Baloo/Configuration
Comment 1 Hamidreza Jafari 2018-07-18 01:08:32 UTC 
It is a matter of developer understanding for the help documentation produced.