| Summary: | Don't index Rust source code | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-baloo | Reporter: | tagwerk19 |
| Component: | Engine | Assignee: | baloo-bugs-null |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
Apparently fixed with Baloo 6.8.0 https://invent.kde.org/frameworks/baloo/-/commit/3e74d49259ffdd519d14dd56888bb1d1c6a1be94 |
SUMMARY: Baloo typically excludes source code via Mimetype exclusion, cf: C++ source with mimetype "text/x-c++src" is excluded. Rust source is not excluded and is therefore indexed (when you have enabled content indexing). STEPS TO REPRODUCE: 1... Enable Baloo content indexing 2... Run: $ balooctl6 monitor (as seems to be the case, you might need to type "balooctl" or "balooctl6") 3... Create a Rust file (something.rs) or download a Rust project... 4... Watch to see the indexing happen on the monitor and/or check what has been indexed with: $ balooshow6 -x something.rs OBSERVED RESULT: Baloo will notice the new/unpacked .rs files and content index them. You will see the internal search terms for the filename after a "File Name Terms:" and the indexed content after a "Plain Test Terms:" when you run balooshow EXPECTED RESULT: Maybe this is not what was wanted and differs from the behaviour with C or C++ code which is not content indexed by default. SOFTWARE/OS VERSIONS: Neon Unstable Plasma: 6.1.90 Frameworks: 6.7.0 Qt: 6.7.2