From: Mark Plaksin <happy@mcplaksin.org>
Subject: Re: Prevent nnrss from generating text/plain parts for HTML text
Date: Wed, 04 Jan 2006 21:38:00 -0500 [thread overview]
Message-ID: <87ek3n4cxj.fsf@stone.tss.usg.edu> (raw)
In-Reply-To: <b4mr77ozmsu.fsf@jpl.org>
Katsumi Yamaoka <yamaoka@jpl.org> writes:
>>>>>> In <87wthiedd8.fsf@stone.tss.usg.edu>
>>>>>> Mark Plaksin <happy@mcplaksin.org> wrote:
>
>> nnrss would be better if it did not generate text/plain parts for items
>> that contain HTML. As-is, when you discourage HTML and an item contains
>> HTML you see the unrendered HTML first. K v will show you the HTML version
>> but it's extra keystrokes.
>
>> I use the this (from Katsumi :) to discourage HTML:
>
>> (setq gnus-buttonized-mime-types
>> '("multipart/alternative" "multipart/signed")
>> mm-discouraged-alternatives
>> '("text/html" "image/.*"))
>
>> Boing Boing's RSS items (from http://boingboing.net/index.xml) are always
>> HTML so I always have to hit K v to read them.
>
>> I don't know the best way to check for HTML in elisp. I've attached a
>> patch which uses a regexp to do the job. The patch works OK for me but I
>> don't think it's ideal. What's a better way to do this?
>
> How about making those variables group parameters?
>
> (eval-after-load "gnus-sum"
> '(setq gnus-newsgroup-variables
> (append '((gnus-buttonized-mime-types
> . '("multipart/alternative" "multipart/signed"))
> (mm-discouraged-alternatives
> . '("text/html" "image/.*")))
> gnus-newsgroup-variables)))
>
> (add-to-list 'gnus-parameters
> '("\\`nnrss:"
> (gnus-buttonized-mime-types nil)
> (mm-discouraged-alternatives nil)))
>
> I haven't fully tested them yet, though.
This works--thanks!
I wonder whether there's any utility to having a text/plain part when
reading RSS feeds. There must be but I can't quite imagine it!
prev parent reply other threads:[~2006-01-05 2:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-02 17:41 Mark Plaksin
2006-01-02 17:51 ` Mark Plaksin
2006-01-04 3:36 ` Katsumi Yamaoka
2006-01-05 2:38 ` Mark Plaksin [this message]
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=87ek3n4cxj.fsf@stone.tss.usg.edu \
--to=happy@mcplaksin.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).