Bug 126009 - disable feed option (without delete)
Summary: disable feed option (without delete)
Status: REPORTED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: 1.2.2
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 136609 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-04-21 11:38 UTC by Mark Veltzer
Modified: 2021-03-09 04:10 UTC (History)
1 user (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 Mark Veltzer 2006-04-21 11:38:22 UTC
Version:           1.2.2 (using KDE 3.5.2, Debian Package 4:3.5.2-2+b1 (testing/unstable))
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.16-1-686

I would like an option to disable a feed. This could be another checkbox in
the "edit feed" general tab.

The reason for this: I know that I can get the effect of disabling the feed
by setting the update interval for a very long period, but this is hardly the same as I would like the update interval value to remain sane and just turn off the feed. Why can't I delete the feed ? Well - it took me time to find the correct link. Why should I lose the link that it took me time to find just because I decided that I wouldn't like to read items from that link for a month ?

Thanks.
Comment 1 Frank Osterfeld 2006-09-04 02:21:39 UTC
How about choosing "Use custom update interval" and set it to "Never"?
That should do it, as long you don't hit the fetch all button.
Comment 2 Mark Veltzer 2006-09-04 10:29:53 UTC
Not the same thing. I explained why this is not a good solution in my original post.
Comment 3 Maarten De Meyer 2012-11-14 14:40:02 UTC
*** Bug 136609 has been marked as a duplicate of this bug. ***
Comment 4 Justin Zobel 2021-03-09 04:10:43 UTC
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.