From: Stefan Huchler <stefan.huchler@mail.de>
To: info-gnus-english@gnu.org
Subject: How to use nnrss-ignore-article-fields
Date: Sun, 26 Jan 2014 14:23:00 +0100 [thread overview]
Message-ID: <87lhy27u8b.fsf@mars.lan> (raw)
I think nnrss-ignore-article-fields is documented to bad. I am not a
total pro emacs user and I am even worse (e)lisp programmer but it
should not be so hard to understand this.
I use rss for youtube feeds and nearly every hour I get 10 old feeds
that I marked as read already again.
It was even hard to find this variable as most likely the mechanism to
stop this.
Then I had to look into the source-code and find a post somewhere that
says that you have to raise the gnus-verbose level to 10 to see output
with what u can maybe find the fields you could put into that.
But even with that it seems that I dont understand what I have to
ignore.
A example output looks like that:
"nnrss: Making hash index of (item nil (guid ((isPermaLink . "false"))
"tag:youtube.com,2008:video:Zx5W7faSEJI") (pubDate nil "Fri, 24 Jan 2014
06:04:18 +0000") (atom:updated nil "2014-01-24T06:21:20.000Z") (category
((domain . "http://schemas.google.com/g/2005#kind"))
"http://gdata.youtube.com/schemas/2007#video") (title nil "Tendresse for
Ten | BSD Now 21") (description nil "<div... [[shortened]] ...</div>")
(link nil
"http://www.youtube.com/watch?v=Zx5W7faSEJI&feature=youtube_gdata")
(author nil "Jupiter Broadcasting"))"
I set and evaluated following list:
(setq nnrss-ignore-article-fields '(slash:comments description atom:updated category title item tag))
but it did not prevent re-appearences of such articles.
I would love to get some help.
Thx
next reply other threads:[~2014-01-26 13:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-26 13:23 Stefan Huchler [this message]
[not found] <mailman.12839.1390742610.10748.info-gnus-english@gnu.org>
2014-01-30 0:18 ` 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=87lhy27u8b.fsf@mars.lan \
--to=stefan.huchler@mail.de \
--cc=info-gnus-english@gnu.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).