GNOME Bugzilla – Bug 221364
Mailer's Search facility doesn't find all locations
Last modified: 2002-03-26 01:02:03 UTC
Please fill in this template when reporting a bug, unless you know what you are doing. Description of Problem: Steps to reproduce the problem: 1. Visit the mail folder whose content I can provide on demand 2. Search for "fomit" 3. Look at the emails found Actual Results: Evolution will *not* find the occurrence of all locations of the word in the folder, ie. it will not find the one in the first email. Expected Results: Find *all* occurrences of the keyword. How often does this happen? Always Additional Information: The problem shows up independant from using the ISO-8859-1 or ISO-8859-15 character set. Another useful information might be the fact, that using non-alphanumeric characters such as [_-{}] will not find *any* location!
Created attachment 41088 [details] This is the mailbox folder which shows the behaviour I described.
search works fast because an indexer indexes by words when mail is incorporated into Evolution. words are split based on non alpha chars. That is why -_{} etc don't work. Searches are not like grep, they are more like a web search.
Hmm, splitting words by non-alpha characters is fine, as long as it works reliably. Please try the attached mbox folder, which contains one message (the first one) that has the word(s) "-fomit-frame-pointer" in it, and search for "fomit" -- note, there's _no_ non-alpha chars in the pattern, still the message won't be found. I'm re-opening this as a bug again.
the indexing stuff is being completely rewritten, also note that searches are not substrings for indexed data. That is 'fom' wont match 'fomit'. Although if you dont have indexing on, it will match. Probably at some point a substring and a string match will be separate 'body match' options, as substring is necessarily significantly less efficient, even with indexing.
substring matches should now work. i.e. fomit will be found, however, -fomit wont (yet, as it contains non-alpha chars). there's another bug covering this situation.