Do you mean that the user should be able to define his own filters? Or that we provide a number of them and the user can choose some of them?

Both!
Ideally, the current filters (Attributes, Local Functions, etc) could be defined from data instead of code.

Ok, I see. I would suggest to write two issues, it's a rather large work package otherwise.

It's a day's work, just borrowing from JDT...

Ok, if you think so... experience says it's never simple to borrow from JDT...

Fixed, but, I took code from JDT, so it's a bit Eclipse 2.0 in style, with its own extension points, etc. I should probably have rewritten the outline to be based on CNF instead...

Updating tickets (#156, #550, #554, #649, #650, #606, #631, #755, #782, #783, #714, #747, #753, #688, #712, #723, #730, #732, #733, #734, #735, #740, #756, #757, #758, #763, #764, #765, #777, #787, #792, #689)

Updating tickets (#723, #730, #732, #733, #734, #735, #740, #753, #755, #756, #757, #764, #782, #787)