| Summary: | should index and search user.xdg.comment | ||
|---|---|---|---|
| Product: | [Unmaintained] Baloo | Reporter: | Richard Z. <rz> |
| Component: | General | Assignee: | Pinak Ahuja <pinak.ahuja> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | b-misc, nate |
| Priority: | NOR | ||
| Version: | 4.13 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Richard Z.
2015-03-22 20:57:32 UTC
I'm going to guess that you're on version 4.13 or 4.14. Please add that info from next time. We have not enabled searching for comments by default. You'll have to type `userComment:"some words"`. This however, will only work with Plasma 5. Could it be enabled by default? Plasma5 or whatever.. but convenience wins. It makes a huge difference in usability for jpeg files where comments are one of the very few ways to reasonably find stuff. (In reply to Richard Z. from comment #2) > Could it be enabled by default? Plasma5 or whatever.. but convenience wins. > > It makes a huge difference in usability for jpeg files where comments are > one of the very few ways to reasonably find stuff. I'm slightly confused. It almost sounds like you're talking about the embedded exif comment wrt jpegs. Though even that isn't searched by default :/ I'm typically not too keen on making this a default as one looses context about search results, specially in places where you don't get to show much info about the file (krunner). In Dolphin you still kind of getting to see the comment if you look in the information panel, but it's not entirely obvious. I like the idea of the user being able to easily understand why results have been shown and making the system as predictable as possible. did not mean exif comments but those entered with dolphin. Imho those comments should have a high priority - if someone enters the information manually he probably considers it pretty important. Especially for picture files tags and comments are the only practical search methods that I know so that kind of search should be pretty easy. How to do that exactly depends on the details of the GUI, dolphin and other tools - if there are easy checkboxes like search comments/tags that would be fine. Re making it clear why some results are shown - I also consider this important but don't think that restricting the results returned will help that goal. Instead it might be interesting to investigate possibilities to present the user additional information about how a particular result was found. Some ideas: * return sub folders of search results (tag-hits, filename-hits, comment-hits, text-search-hits) * find a way to display search result snippets Perhaps we do want them searchable by default. Leaving this open for now. *** Bug 340535 has been marked as a duplicate of this bug. *** Comments are indexed now. |