Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
[feature] selectively update feeds #109
I'd like to be able to update some subset of the feeds in elfeed-feeds, say only the feeds which are currently providing entries in elfeed-search. Here's a quick mockup:
I think it needs to be a little bit fancier. It should act as if no 'unread' tag is present, to bring new entries into the results. And it should only activate selective update on C-u G.
How about something like this? Much faster to update a small subset of a large collection of feeds.
added a commit
Nov 20, 2015
This is a great idea. Way back I considered a feature for updating feeds
However, your idea builds directly on top of the existing filter
I made a fetch-visible feature branch, which you should see associated
I regret using the word "update" in the search buffer to refer to
I'm still wondering about this case though:
You have some search defined and it selects entries from two feeds. You read some of the entries and leave some longer ones for later, and it just so happens that all entries from one of the feeds have been read, or they fall outside your time restriction, and therefore none show up in the search.
Your intention now when you press C-u G is "show me more like the ones I've just read". ie: show me entries that would be visible, if the database was up to date. But this doesn't work.
One way around this gotcha is to document it and say: you probably want to extend any short dated time restriction and remove the +unread tag from your search, press C-u G, then re-add those restrictions to get what you probably expect.
Another way would be to automatically modify those search terms before running fetch-visible, although ideally this would happen off-screen to prevent a flash of old entries.
Anyway, fetch-visible is a neat improvement so far!
One of my core guidelines for Elfeed's interface is that it shouldn't be
"Update exactly what I currently see" is obvious. With the way I
Another core guideline is composability and extensibility. Given
In your case, I'd like to first try implementing the idea as an
Yup, I agree. The corner cases occurred to me and the solution above was more or less me just talking out loud.
Anyway, I've been poking at it a bit more and came up with these two manual toggles:
With them you can quickly toggle the unread tag and date restriction. Feels pretty good, and no need for weird auto-magic behaviour in the updating.