Gnus development mailing list
 help / color / mirror / Atom feed
From: Nelson Ferreira <nelson.ferreira@ieee.org>
Subject: Re: Selective HTML rendering using group parameters
Date: Wed, 15 Mar 2006 03:05:37 -0500	[thread overview]
Message-ID: <m3zmjs3zfy.fsf@tuxie.homelinux.net> (raw)
In-Reply-To: <m3bqw85ju6.fsf@tuxie.homelinux.net>


An update below...

"njsf" == Nelson Ferreira <nelson.ferreira@ieee.org> writes:

    njsf> Hi all,
    njsf> I came across a weird issue regarding group-parameters and
    njsf> "group-local" variables.

    njsf> I have the following in my gnus:

    njsf> ,---- .gnus ----
    njsf> | (setq 
    njsf> |  mm-automatic-display (remove "text/html" mm-automatic-display)
    njsf> |  mm-discouraged-alternatives '("text/html" "text/richtext" "text/enriched" "multipart/related")
    njsf> |  )
    njsf> `----

    njsf> in order to have HTML rendering off by default.  However
    njsf> there are some mailing lists I subscribed where the HTML is
    njsf> well-formed enough (and there is no option for text-only :(
    njsf> ) where I wanted to enable html rendering by default on
    njsf> those groups.

    njsf> So I tried the following in the group parameters of one of
    njsf> the groups with "good" HTML:

    njsf> ,---- group parameters ---
    njsf> | ((mm-automatic-display
    njsf> |   (append
    njsf> |    (list "text/html")
    njsf> |    mm-automatic-display))
    njsf> |  (mm-discouraged-alternatives
    njsf> |   (remove "text/html"
    njsf> |           (remove "multipart/related" mm-discouraged-alternatives))))
    njsf> `----

    njsf> Sure enough if I press space from the *Group* buffer, the
    njsf> HTML in the message is rendered, and it so happens in all
    njsf> other messages in that "summary buffer session" .

    njsf> However, if no message is immediately rendered (I press
    njsf> ENTER or only ticked articles are in the summary buffer)
    njsf> then when the article is shown, the HTML is not rendered.

    njsf> I looked at the value of both mm-automatic-display and
    njsf> mm-discouraged-alternatives and it looks like that if upon
    njsf> entering the group the article buffer is created then
    njsf> their values are the one coming from the group parameters,
    njsf> otherwise the defaults (i.e. from .gnus) are used.

    njsf> Is there any way to make sure that the group parameter set
    njsf> values for variables are always transported to the article
    njsf> buffer regardless of the moment in time it is created ?

I tried adding mm-automatic-display and mm-discouraged-alternatives
to gnus-summary-local-variables and then playing with .gnus to set
the default value and the group parameters to deal with getting the
default and changing it in the group parameters with mostly the same
results.

Thanks,

        Nelson


[...]

-- 
Nelson Ferreira




  reply	other threads:[~2006-03-15  8:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-15  5:59 Nelson Ferreira
2006-03-15  8:05 ` Nelson Ferreira [this message]
2006-03-15  8:56 ` Katsumi Yamaoka
2006-03-15 20:20   ` Nelson Ferreira

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=m3zmjs3zfy.fsf@tuxie.homelinux.net \
    --to=nelson.ferreira@ieee.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).