From: Glenn Shiffer <fubar@pobox.com>
Subject: Re: html buttons in pgnus 0.84?
Date: 29 May 1999 07:12:53 -0400 [thread overview]
Message-ID: <84pv3kqgcq.fsf@pobox.com> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "19 May 1999 19:57:38 +0200"
Tried it and it's the same old thing- html code displayed in-line, no
button :(.
Just for mentioning I'm using pgnus .84 in xemacs 20.4 under Solaris 7
(32 bit) on a Sparc 2.
And yes, I agree, this is way to complicated. It's nice that gnus
will grok mime internally, but as things stand right now, it's a long
way from tm.
We'll just have to keep plugging away. Which brings me to asking-
where can I get more information on the workings of pgnus/mime then is
available in the FAQ and manual?
Glenn
>>>>> "Kai" == Kai Grossjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:
Kai> Glenn Shiffer <fubar@pobox.com> writes:
>> I have the browser function variable set to Netscape and have
>> included the following in my .gnus (at Kai's suggestion):
>>
>> (add-to-list 'mm-inline-media-tests '(text/html mm-inline-text
>> nil))
Kai> What happens if you also do the following?
Kai> (setq mm-user-automatic-display (remove "text/html"
Kai> mm-user-automatic-display)) (add-to-list
Kai> 'mm-user-automatic-external-display "text/html")
Kai> For me, Gnus now asks whether to save the HTML stuff. Not
Kai> quite what we wanted, but maybe a start?
Kai> This seems to be way too complicated... :-|
Kai> kai
--
Glenn Shiffer fubar@pobox.com
__ __
/ // /___ (_)__ __
/ // // _ \ / /\ \/ / . . . t h e c h o i c e o f t h e
\_,_//_//_//_/ /_/\_\ G N U g e n e r a t i o n.
next prev parent reply other threads:[~1999-05-29 11:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-18 11:21 Glenn Shiffer
1999-05-19 17:57 ` Kai.Grossjohann
1999-05-29 11:12 ` Glenn Shiffer [this message]
1999-05-31 9:12 ` Kai.Grossjohann
1999-06-12 23:42 ` Lars Magne Ingebrigtsen
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=84pv3kqgcq.fsf@pobox.com \
--to=fubar@pobox.com \
/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).