feature: partial update

[mlavrinenko]

I use the "Inbox Zero" method, so I delete everything I've processed.
But this is not possible with Bulletty.
Each entry I delete immediately reappears at the next bulletty update.

.feed.toml stores lastupdated, and it would be easy to ignore all entries with date < feed.lastupdated when updating.

Sounds like an easy fix, and I could contribute it, but maybe I'm missing something and this would be useless work?
I may implement this as an option for the update command to avoid any BC (breaking change) in behavior.
I'll do a PR once I get confirmation that it can be accepted.

[crocidb]

Hi @mlavrinenko,

Interesting, I never thought about it, just like I never thought that anyone would ever want to delete a text.

But I really like what you propose. Maybe, we could have a .config.toml file within the library directory having a soft-update property indicating if we want to do a soft update or a regular one. When that is true, all the update operations (cli and tui) should follow your rule of checking the last updated. I'd love to merge it!

That would pair really well with #154, especially if we had a confirm dialog explaining the current behavior (if it's a soft-update, telling the user that that article will never come back, otherwise, telling that it will come back). :)

Thanks!