kerry matches "elias@asb" when searching for "elias_asb"

test by searching for know email address part but replacing @ with _

This is not straight like I described above. When I search for elias@asb kerry shows 3 results. In fact these results are all emails to this bug tracking system containing the exact phrase "elias@asb" but not the real email addess which is <email address hidden>.

But when I search for elias_asb, which is actually only in these same 3 mails and in the one text file which I was searching for initially I get 106 results!

Most of them are emails which contain my email address somwhere in the message, some contain an backtrack url containing my email address. But some do not contain the address at all. The address was just the recipient and of course the whole address, not just the subpart elias@asb.

Very very strange!

Further investigation has shown, that the source code of the email in question actually contain the elias_asb string!

X-Original-To: <email address hidden>
Delivered-To: <email address hidden>

So, seems this is not a bug after all!

but here more observation:

kerry feels significantly slower then beagle-search when there are more results, most likely due to the fact that it does not show anything before it is finished.

that should be changed. moreover nothing in kerry indicates that a search is in progress. the app does not respond to interaction anymore as soon as a search is in progress, you cant stop or change your search, all in all it looks like the app has crashed.

therefore I recommend to make a beagle_search like approach where results are shown as soon as they are found. and you can change the search string any time. it also is nice if the search starts with the first letter typed with no need to hit "find now".

beagle_search finds more documents then kerry does: 25:28 when searching for an IP address.

eventhough I like the fact that kerry gives a lot of info about the found files that should be done in a more organized manner. ordering by document type is desirable!

the results should also be presented in a less space consuming way. just loose the whitespace. The fact that kerry shows where the search sequence has been found in the document should not be compromised but compressed.

Closing this report due to lack of activity and the reporter stated it was not a bug. If you feel this initial issue is still a problem, I urge you to reopen this report. Thank you.