From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: nnrss group doesn't wash multipart article correctly
Date: Tue, 09 Dec 2008 17:27:17 -0600 [thread overview]
Message-ID: <86ljupylnu.fsf@lifelogs.com> (raw)
In-Reply-To: <8763ltng00.fsf@topper.koldfront.dk>
On Tue, 09 Dec 2008 23:25:03 +0100 asjo@koldfront.dk (Adam Sjøgren) wrote:
AS> On Tue, 09 Dec 2008 15:50:17 -0600, Ted wrote:
>> Can I configure this group in particular to apply HTML washing? I
>> didn't see such an option in the manual or in the code.
AS> I have set these group parameters (G p) on the nnrss groups I have that
AS> contain HTML:
AS> ((gnus-treat-wash-html t))
AS> ... seems to work alright for me.
Ah. In the manual there's a link at the bottom and the top of Article
Washing to Customizing Articles, which I followed but then didn't see a
way to apply those to a specific group. The manual node says
'To have them called automatically, you should set the corresponding
"treatment" variable. For instance, to have headers hidden, you'd set
gnus-treat-hide-headers.
...
You can, of course, write your own functions to be called from
gnus-part-display-hook. The functions are called narrowed to the part,
and you can do anything you like, pretty much. There is no information
that you have to keep in the buffer--you can change everything.'
This is not helpful to someone who doesn't know how to set
gnus-treat-hide-headers in the group parameters; `G c' is not helpful
because it has no way to specify those parameters. I couldn't figure it
out and thought the above could only be done in a hook.
Should I:
a) implement something for `G c' that will let users add treatments to a
group/topic, or
b) add examples to the manual of how to do the above, or
c) both (including a `G c' reference in the manual node)?
Thanks
Ted
next prev parent reply other threads:[~2008-12-09 23:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-09 21:50 Ted Zlatanov
2008-12-09 22:25 ` Adam Sjøgren
2008-12-09 23:27 ` Ted Zlatanov [this message]
2008-12-11 18:21 ` Ted Zlatanov
2008-12-11 20:02 ` Adam Sjøgren
2008-12-11 20:55 ` Reiner Steib
2008-12-12 21:51 ` Ted Zlatanov
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=86ljupylnu.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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).