From: prj@po.cwru.edu (Paul Jarc)
Cc: jesseh@cs.kun.nl (Jesse F. Hughes)
Subject: Re: Question about HTML emails (revisited)
Date: Thu, 01 Aug 2002 14:37:42 -0400 [thread overview]
Message-ID: <m3znw6tofn.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <87sn1z397b.fsf@phiwumbda.localnet>
jesseh@cs.kun.nl (Jesse F. Hughes) wrote:
> jesseh@cs.kun.nl (Jesse F. Hughes) writes:
>> prj@po.cwru.edu (Paul Jarc) writes:
>>> jesseh@cs.kun.nl (Jesse F. Hughes) wrote:
>>>> (mm-automatic-display
>>>> (cons "text/html" mm-automatic-display))
>>>
>>> I don't think this will work. mm-automatic-display will be set to the
>>> literal value '("text/html" . mm-automatic-display);
Actually, the more sensible literal expectation would be the list
'(cons "text/html" mm-automatic-display); i.e., both cons and m-a-d
would be treated as uninterpreted symbols.
> The problem is that the commands below set the default value of
> mm-automatic-display to nil. This is where you run into troubles.
...
>>> (require 'gnus-sum)
>>> (add-to-list 'gnus-newsgroup-variables 'mm-automatic-display)
>>> (add-to-list 'gnus-newsgroup-variables 'mm-discouraged-alternatives)
I'd say that's a bug, but you could probably work around it with
something like this:
(setq gnus-parameters
`(("" ;; explicitly specify the defaults
(mm-automatic-display ,mm-automatic-display)
(mm-discouraged-alternatives ,mm-discouraged-alternatives))
("\\`nnslashdot[+:]" ;; override for nnslashdot groups
(mm-automatic-display
,(cons "text/html" mm-automatic-display))
(mm-discouraged-alternatives
,(remove "text/html"
(remove "text/richtext" mm-discouraged-alternatives))))))
This assumes you first set m-a-d and m-d-a to the appropriate values
for non-slashdot groups.
paul
parent reply other threads:[~2002-08-01 18:37 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <87sn1z397b.fsf@phiwumbda.localnet>]
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=m3znw6tofn.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
--cc=jesseh@cs.kun.nl \
/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).