From: wmperry@aventail.com (William M. Perry)
Cc: ding@gnus.org
Subject: Re: text/enriched?
Date: 14 Sep 1998 10:45:56 -0500 [thread overview]
Message-ID: <86k936snnv.fsf@kramer-fast.bp.aventail.com> (raw)
In-Reply-To: Conrad Sauerwald's message of "14 sep 1998 16:38:20 +0200"
Conrad Sauerwald <conrad@stack.nl> writes:
> Colin Marquardt <C.Marquardt@alcatel.de> writes:
>
> > > Yes, I think so, but I don't have any text/enriched, so it's a bit
> > > difficult to try it out...
> >
> > Help|Samples|Sample enriched ???
>
> Depending on which of the emacsen you use, for example FSF Emacs 20.3
> see /usr/local/share/emacs/20.3/etc/enriched.doc
>
> And while on topic, mm.el contains the following entry:
>
> ("enriched" . (("viewer" . enriched-decode-region)
> ("test" . (fboundp
> 'enriched-decode-region))
> ("type" . "text/enriched")))
>
> which very probably needs to check for enriched-decode instead of
> enriched-decode-region.
> This was just patched in pgnus 0.31 (which then has text/html-like
> support for inline display of text/enriched), but beware if you have
> w3 installed as well and thus have two "competing" mm.el files.
Lars - when you feel satisfied that your changes to mm.el are settling
down, send me a copy and I'll update the Emacs/W3 version, and we can split
it out into it's own distribution or something like that.
-Bill P.
next prev parent reply other threads:[~1998-09-14 15:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-14 7:27 text/enriched? Kai Grossjohann
1998-09-14 12:36 ` text/enriched? Lars Magne Ingebrigtsen
1998-09-14 13:33 ` text/enriched? Colin Marquardt
1998-09-14 14:25 ` text/enriched? Lars Magne Ingebrigtsen
1998-09-14 14:38 ` text/enriched? Conrad Sauerwald
1998-09-14 15:45 ` William M. Perry [this message]
1998-09-15 7:36 ` text/enriched? Kai Grossjohann
1998-09-15 8:15 ` text/enriched? Conrad Sauerwald
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=86k936snnv.fsf@kramer-fast.bp.aventail.com \
--to=wmperry@aventail.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).