GNOME Bugzilla – Bug 343450
E-mail "start with" filter requires an extra leading space to work
Last modified: 2012-02-09 14:58:49 UTC
That bug has been opened on https://launchpad.net/distros/ubuntu/+source/evolution/+bug/39554 "... It appears as if 'Subject starts with "[Bug"' doesn't work. However, 'Subject contains "[Bug"' works. It might be a problem with the "stars with" filter. ... in evolution 2.6.1-0ubuntu7 it is the same. the filter rule "subject start with" don't work. if i change the rule to "contain"-condition it works fine. ..." using a space to the filter between the actual string starting the title seems to fix the issue
sounds a bit similar to bug 343316.
Subject: foo bar ---- starts with " foo" Subject:foo bar --- starts with "foo"
* start evolution * write a new mail * use "subject" as subject you typed "subject", when you receive the mail the preview pane has "subject" selectable with no space before, the space added by the mailer after the ":" is a technical detail the user should not have to care about it
confirming as per duplicate.
*** Bug 349346 has been marked as a duplicate of this bug. ***
Confirming on Evolution 2.9.4. This was also reported downstream: http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=206485 Interesting that search folders with "subject starts with" rules don't exhibit this problem.
I agree (after a while thinking on it) that the filter code should strip leading lwsp
Created attachment 86086 [details] [review] the patch attempts to increment the pointer pointing to the the subject as long as there is a space in the beginning
that loop already did what you are trying to make it do :) camel_utf8_getc() increments ptr to the end of the char it returns, if it didn't - that loop would be an infinite loop :)
*** Bug 400304 has been marked as a duplicate of this bug. ***
Looks like a problem with compiler, when I remove keyword "inline" before function camel_utf8_getc in camel-search-private.c, then everything works like expected. With this inline declaration it works wrong. Maybe a bug for gcc? My gcc version is: gcc (GCC) 4.1.2 20070424 (Red Hat 4.1.2-11)
I fixed this issue at bug #469007, which is resolved/fixed now, and this can be marked as a duplicate of that one (because that one contains a patch for this). You can see that this works with actual Evolution (2.11.92). Feel free to close this bug.
That's still an issue according to the ubuntu user who replied to the comment
Can you check, somehow, if he uses "right" version in Gutsy (with applied patch) and if he doesn't have there a preceding space in a value for which rule looks? (I meant, if he didn't forget that space in the rule because of a workaround to let it work on ancient Evolution.) Because the patch isn't there so long, it's in 2.12.0 only two weeks. And what's his architecture? This was only for 64bit, AFAIK.
I think this may be fixed now in 2.12 (see bug #370012). Can someone confirm?
This works correctly in 3.2.3. Closing. *** This bug has been marked as a duplicate of bug 370012 ***