Version: (using KDE 3.5.9) Installed from: Ubuntu Packages When moving articles to different folders, only the article should be copied, not the whole feed. In Thunderbird and other RSS clients, individual RSS entries can be moved to different folders much like individual email messages. Currently Akregator moves the entire feed. I have folders such as "funny", "important", and others that I want to move different RSS entries too. The current Akregator cannot separate entries from the rest of the feed.
I am updating the Summary to better express the bug. Basically the bug is asking that individual RSS feed entries be treated like Kmail email messages in the sense that one could move them to different folders. Usage scenario: Joe User subscribes to an RSS feed for his university. All his assignments come in on the same feed. He creates folders for each subject and needs to sort the feed entries into their individual folders. Currently, this is impossible in Akregator. Other RSS clients, such as Thunderbird, can do this.
I also think that would be a really great feature. In addition to Dotan Cohen, I would like to add the following: If every article would be an individual item, articles could also be (easily): - moved to some kind of Trash (folder) and back, like in KMail (see bug 166183 & others) - syncronized on different computers over whatever protocol/connection (there was a bug/wish concering this somewhere) - ported from one installation of akregator to another, for distro-hoppers like me ;-) - imported and exported to a file, for e.g. sharing via EMail -... If Thunderbird already has this ability, there even is a clear example of e.g. which file formats we could use (for interoperability, too). I know that would (still) be quite a change in the akregator concept and code, but I think it's worth it, considering the amount of flexibility akregator would gain... please consider it...
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.