Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: nnrss group doesn't wash multipart article correctly
Date: Thu, 11 Dec 2008 21:55:04 +0100	[thread overview]
Message-ID: <87k5a6e8k7.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <86ljupylnu.fsf@lifelogs.com>

On Wed, Dec 10 2008, Ted Zlatanov wrote:

> On Tue, 09 Dec 2008 23:25:03 +0100 asjo@koldfront.dk (Adam Sjøgren) wrote: 
> AS>   ((gnus-treat-wash-html t))
> AS> ... seems to work alright for me.
[...]
> 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

Doesn't adding them within "Variables" work?

,----[ `G c' -> *Gnus Customize* ]
| Variables:
| Set variables local to the group you are entering. [Hide Rest]            
|             
|     If you want to turn threading off in `news.answers', you could put
|     `(gnus-show-threads nil)' in the group parameters of that group.
|     `gnus-show-threads' will be made into a local variable in the summary
|     buffer you enter, and the form nil will be `eval'ed there.
|     
|     This can also be used as a group-specific hook function, if you'd
|     like.  If you want to hear a beep when you enter a group, you could
|     put something like `(dummy-variable (ding))' in the parameters of that
|     group.  `dummy-variable' will be set to the result of the `(ding)'
|     form, but who cares?
| [INS] [DEL] Variable: gnus-treat-WHATEVER
|             Value: foo-bar
`----

> b) add examples to the manual of how to do the above, or

> c) both (including a `G c' reference in the manual node)?

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/




  parent reply	other threads:[~2008-12-11 20:55 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
2008-12-11 18:21     ` Ted Zlatanov
2008-12-11 20:02       ` Adam Sjøgren
2008-12-11 20:55     ` Reiner Steib [this message]
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=87k5a6e8k7.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --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).