Version: (using KDE 4.0.83) Installed from: Ubuntu Packages Please add a Trash folder to Akregator. Bug 119726 asked for trash or one-touch delete, but was closed without implementing the Trash option. Note that this bug might depend upon Bug 165664 as it would require moving one entry without moving the entire feed.
*** Bug 190614 has been marked as a duplicate of this bug. ***
(I am commenting this bug because mine - 190614- was an accidental duplicate. Sorry for that) I understand the current Akregator concept cannot have a trash because articles are'nt individual items. I will comment on bug 165664 considering this. But for a quick solution, I think there could be a workaround: Basically, we would just need an 'UNDO' option in the toolbar or somewhere. I don't know how complicated that would be, but I guess not so much, and a basic 'Undo remove last article' would suit 99% of my needs anyway. If you'd even want multiple UNDO levels, there could be some textual representation of the articles - not the actual 'items'! - and thus a 'fake trash'. It would be up to you to decide if that's just for the last item removed, or all removed ones since starting akregator, or whatever.
Trash bin has a different function than moving between folders. Trash is a kind of default for items that you move by pressing delete button. With a normal, regular folder user need to choose where to move item, there is no this default presupposition that it has to land in once predefined so called "trash" folder. It is just different functionality. I don't know how it look from programming point of view but eventually it should be implemented. After all it is quite a basic functionality. People vote for it: http://forum.kde.org/viewtopic.php?f=83&t=95963 As it was reportet in 2008, please make it happen eventually. Lack of trash in Akregator is the only reason I still use Thunderbird.
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.