Discussion:
limited view and incoming messages
Vincent Lefevre
2018-07-02 23:34:40 UTC
Permalink
I sometimes use a limited view with: ~(~asome_address)

But in such a case, incoming messages that match this pattern are
not included in this limited view. Is this a bug or a feature with
particular patterns?
--
Vincent Lefèvre <***@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Kevin J. McCarthy
2018-07-03 17:06:43 UTC
Permalink
Post by Vincent Lefevre
I sometimes use a limited view with: ~(~asome_address)
But in such a case, incoming messages that match this pattern are
not included in this limited view. Is this a bug or a feature with
particular patterns?
It's probably some technical difficulty. I'll try to poke around and
see if I can figure out why.
--
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
Kevin J. McCarthy
2018-07-20 03:44:26 UTC
Permalink
Post by Kevin J. McCarthy
Post by Vincent Lefevre
I sometimes use a limited view with: ~(~asome_address)
But in such a case, incoming messages that match this pattern are
not included in this limited view. Is this a bug or a feature with
particular patterns?
It's probably some technical difficulty. I'll try to poke around and
see if I can figure out why.
This patch is "work in progress", but you are welcome to try it out.

The difficulty was in the update_index() function, where it applied the
limit first and then sorted. For ~(pattern) we need thread information
for the new messages, requiring an initial sort, and then a pattern match.

Unfortunately, one more call to sort is needed to properly set virtual
numbers and redraw the tree. This will only be done when a limit is in
effect through.

Again, this is WIP - I need to test and clean it up still.
--
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
Loading...