Dear gentoo team: It is finally dawning on me why I have filed so many duplicate bug reports. I am probably not the only one, so I hope this suggestion will make Jakub's task easier. A bug search for "cairo ALL" gives 1 result. A search for "cairo" yields 19 results. A search for "ALL cairo" yields the complete set of results. A naive user like me thinks that "ALL" suffixed should give the same answer as affixed. either this should be explained where you say "affix" (i.e., in big red, order matters---don't say 'searchterm ALL', cause it won't work); or reorder the "ALL" term automatically. regards, /ivo
ALL cairo
Hi Jakub: I understood this. My point is that bugs.gentoo.org has a very strange search engine from the perspective of a naive user (like myself). Most of us will think that searching for "a b" is the same as searching for "b a", and especially if b is a modifier. I also noted this as a request for an enhancement, not a bug. If this is enhanced, my guess is that invalid duplicate bug requests are going to fall by 50%, best, /ivo
Moving open bugzilla bugs to the new bugzilla group (because I'm about to stab lots of these bugs).
frontpage used to say affix. it now explictly says PREFIX.
"When searching for duplicate bugs or using multiple search terms, prefix your entry with 'ALL' (not suffix) " Suggestion for change: "When searching for duplicate bugs or using multiple search terms, prefix your entry with 'ALL' (don't suffix). Also, word search order matters! " I still consider the fact that word order matters an undesireable. optimally, you would simply take the set of all results of all permutations that currently match. It has to be rare that someone searching for a bug would not want to see permutation searches (which is what would be lost). regards, /iaw
ALL is not a term in the regular sense. And without changing a lot of code, it's not really easy to get any-position ALL to work. The two searches: (a b) (b a) are identical. Word order does NOT matter. Putting ALL at front of the query, it is specially picked up by the simple search form, which widens the set of resolutions and status flags that it searches under. Can I close this again now.
Just close this; there's absolutely no way to do what's requested in Comment #5 until upstream make this stuff configurable as opposed to hacking the source code which makes any upgrade a huge PITA, sorry.
thanks, guys.
