Bug 176396 - read articles don't disappear after reading when status: unread
Summary: read articles don't disappear after reading when status: unread
Status: RESOLVED UNMAINTAINED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Unspecified
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-29 02:36 UTC by Sebastiano
Modified: 2017-01-07 22:38 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sebastiano 2008-11-29 02:36:53 UTC
Version:            (using KDE 4.1.3)
Installed from:    Ubuntu Packages

Suppose the status is set to unread and the list of unread articles is presented (in red).
I then click on the first article to read it, and then on the second one. Since only unread articles should be displayed, clicking on the second article should trigger a removal of the first article from the list. Instead what happens is that the title of the first article turns from red to black.
Comment 1 Elias Probst 2008-11-29 23:45:56 UTC
Can confirm this behaviour.
List is only updated by changing the view mode to something different (.e.g 'All') and back again.
Comment 2 Frank Osterfeld 2008-11-30 21:58:53 UTC
That's on purpose. It should be possible to go back to the previously read article when going through unread items no matter the filter. 
Comment 3 Sebastiano 2008-12-01 08:17:22 UTC
Dear Frank,

sorry but I don't agree with your reply. If I want to see the read articles I choose the all articles - filter, if not I choose the unread - filter. I thought that's the point of having the filter?

As it is, if I don't randomly change my view mode every once in a while I have a filter set on unread and hundreds of read articles (I don't turn my computer off/restart akregator).

Possible options that come to my mind (if it's not possible to clean the list when clicking on the next article): clear read articles from list when feeds are fetched / add a clean list button to the toolbar.

Best regards, Sebastiano
Comment 4 Manuel Schmid 2009-02-25 22:54:08 UTC
I am facing the same issue and it is in fact one of the only things that bug me about Akregator. I agree with Frank that instantly removing the articles is not the best option, as I sometimes go to the next article too quickly and it is really hard to find an article if you don’t know which feed it’s from.

However, I see two viable solutions:
1) As Sebastiano suggested, create a toolbar button to clean/update the list, where read items are removed.
2) Clean/update the list when the window is closed.

This would support the workflow, where you Akregator, read all new articles, close it to tray and open it again whenever new articles appear.

At the moment I use two suboptimal solutions, the first being setting the filter to unread again, the second being clicking on the ‘all news sources’ entry in the feed list, every time on a different column.

I would love to see this workflow improved, with solution 2) being my favourite, as it requires no additional clicks. https://bugs.kde.org/show_bug.cgi?id=114263 is also about this issue.
Comment 5 Marcel Dischinger 2010-12-15 13:24:40 UTC
I can see that messages are not immediately cleaned when moving between messages. 

But if I click on "Mark Feeds as Read" I actually expect the read messages (i.e., all messages) to disappear from the list. This could happen for all messages that are explicitly marked as read.
Comment 6 Denis Kurz 2016-09-24 19:43:32 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of akregator (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 7 Denis Kurz 2017-01-07 22:38:52 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.