You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Newsboat version (copy the output of newsboat -v or the first line of git show):
r2.21-362-g80f1
Steps to reproduce the issue:
Apply a filter by pressing F and type in title =~ "(string that's only in a subset of articles)"
Press A to mark all read.
Expected: only visible articles are read, similar to if one had used / (open-search) to do the filtering instead of a filter.
Actual: all articles in the feed are read.
My guess is this happens because / creates a temporary "feed" and marks it read, while filters work differently? Anyway, seems like they should work the same, or perhaps a new mark-visible-read command could be added?
The text was updated successfully, but these errors were encountered:
5163927 (PR #1558) changed
mark-all-read to mark each item individually. That made mark-all-read
aware of the filters, but also made it slower. This was especially
noticeable with remote APIs, where mark-read latency is high.
We can't speed it up in the general case, but when there is no filter,
we can fall back onto the faster mark_all_read() method which marks the
entire feed in one go. I tested that this new code is indeed faster and
doesn't re-introduce #1364.
Reported by Oneiric on IRC.
Newsboat version (copy the output of
newsboat -v
or the first line ofgit show
):r2.21-362-g80f1
Steps to reproduce the issue:
Apply a filter by pressing
F
and type intitle =~ "(string that's only in a subset of articles)"
Press
A
to mark all read.Expected: only visible articles are read, similar to if one had used
/
(open-search
) to do the filtering instead of a filter.Actual: all articles in the feed are read.
My guess is this happens because
/
creates a temporary "feed" and marks it read, while filters work differently? Anyway, seems like they should work the same, or perhaps a newmark-visible-read
command could be added?The text was updated successfully, but these errors were encountered: