all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Tim Landscheidt <tim@tim-landscheidt.de>
Cc: 45477@debbugs.gnu.org
Subject: bug#45477: 27.1; RFE: Make full RSS fragments available for nnrss servers
Date: Thu, 31 Dec 2020 05:33:00 +0100	[thread overview]
Message-ID: <87mtxuoarn.fsf@gnus.org> (raw)
In-Reply-To: <87czyrn1oo.fsf@passepartout.tim-landscheidt.de> (Tim Landscheidt's message of "Wed, 30 Dec 2020 08:22:15 +0000")

Tim Landscheidt <tim@tim-landscheidt.de> writes:

> Even if the XML gets bloated when saved in nnrss-group-data
> (it holds one feed at most), IMHO almost all feeds will be
> small enough to be negligible in a typical Emacs/Gnus setup
> (the largest feed above holds data from February 2010 till
> now; usually feeds only contain the most recent x entries).

Doesn't nnrss-group-data store older entries, though?  I just skimmed
the nnrss code, and I didn't see any pruning...

>> I think a way to implement this would be to add an nnrss variable that
>> says what "extra" XML fields to store -- like (nnrss-extra-fields
>> '(itunes:episodeType ...)).
>
> That would allow my use case.

Patches welcome.  :-)

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2020-12-31  4:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-27 21:30 bug#45477: 27.1; RFE: Make full RSS fragments available for nnrss servers Tim Landscheidt
2020-12-28  0:05 ` Lars Ingebrigtsen
2020-12-29 16:50   ` Tim Landscheidt
2020-12-30  3:02     ` Lars Ingebrigtsen
2020-12-30  8:22       ` Tim Landscheidt
2020-12-31  4:33         ` Lars Ingebrigtsen [this message]
2021-01-01 17:09           ` Tim Landscheidt
2021-01-02  5:52             ` Lars Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mtxuoarn.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=45477@debbugs.gnu.org \
    --cc=tim@tim-landscheidt.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.