https://bugs.kde.org/show_bug.cgi?id=445402
--- Comment #3 from Tony <antonio.dimarti...@gmail.com> --- (In reply to Nate Graham from comment #2) > Yes, these search interfaces truncate the results after a few to prevent a > truly ridiculous, unparseably long list from being shown and being too > scary. If you've found that you searched for something that what you > expected didn't come up because it would be too low on the list, just keep > typing to refine the search. >unparseably long list from being shown and being too scary. Nate, i'm doing a semantic search, i'm ready to face a lot of results and a scrollbar is perfectly fine to read them all. > just keep typing to refine the search. I've tried and it doesn't work: i'm searching for the book (whose title i don't remember) that contains the argument "steering vector" (radar related) and it doesn't appear. What else should i have to add to find it? If i remembered all the details, what would be the search function for? I'm searching just because i don' t remember the details (where the book is located and what's its name). Another consequence of this choice is that user doesn't know if Baloo is working properly. At a first glance i thought a malfunction in Baloo and rebuilt the database; in the end i discovered the change. This way we have two entry point for search that work differently: one is half working (kickoff) and makes me lose time, the other (dolphin) is working as expected. At this point, it would be better to remove search from Krunner, if i'm forced to open dolphin. Please, rethink about this. Regards. -- You are receiving this mail because: You are watching all bug changes.
