From: wmperry@aventail.com (William M. Perry)
Cc: ding@gnus.org
Subject: Re: Writing enriched text
Date: 21 Apr 1999 09:22:03 -0500 [thread overview]
Message-ID: <86676q6ol0.fsf@kramer.bp.aventail.com> (raw)
In-Reply-To: Laura Conrad's message of "21 Apr 1999 09:42:12 -0400"
Laura Conrad <lconrad@concord.com> writes:
> wmperry@aventail.com (William M. Perry) writes:
>
> > You would of course want this configurable, similar to how netscape lets
> > you do it:
> >
> > 1. Always send only HTML email
> > 2. Never send HTML email
> > 3. Always send HTML with text/plain alternative
> > 4. Ask the user
>
> But, unlike netscape, we would NOT make 3 the default.
>
> I assume we would also set up some configuration variable so that
> users could vary this by group or to-address or whatever.
Could be done via a posting-style type variable, or a group property. You
could have something like
(defcustom message-html-posting-style 'ask
"*Controls how and when to post HTML email."
:group 'message
:type '(choice (const :tag "Ask when necessary" ask)
(const :tag "Always send only HTML" html)
(const :tag "Always send HTML and plain text" both)
(const :tag "Never send HTML" never)
(sexp :tag "Custom function" nil)))
-Bill P.
next prev parent reply other threads:[~1999-04-21 14:22 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-20 20:55 François Pinard
1999-04-20 21:26 ` Colin Rafferty
1999-04-20 21:43 ` Hrvoje Niksic
1999-04-20 21:44 ` François Pinard
1999-04-21 13:49 ` Colin Rafferty
1999-04-21 14:09 ` Kai.Grossjohann
1999-04-21 14:43 ` Colin Rafferty
1999-04-22 15:04 ` Kai.Grossjohann
1999-04-22 15:24 ` Colin Rafferty
1999-04-22 16:01 ` Kai.Grossjohann
1999-04-23 12:56 ` Hrvoje Niksic
1999-04-23 13:25 ` Kai.Grossjohann
1999-04-23 13:37 ` Hrvoje Niksic
1999-04-23 14:58 ` William M. Perry
1999-04-23 15:45 ` Per Abrahamsen
1999-04-22 15:55 ` Jan Vroonhof
[not found] ` <vaf676o7l3p.fsf@ramses.cs.uni-dortmund.de <byd80whcpl.fsf@bolzano.math.ethz.ch>
1999-04-22 16:54 ` Colin Rafferty
1999-04-20 21:52 ` David Hedbor
1999-04-20 22:42 ` Hrvoje Niksic
1999-04-20 23:08 ` Bruce Stephens
1999-04-20 23:20 ` David Hedbor
1999-04-21 0:04 ` enriched bug (was Re: Writing enriched text) Stainless Steel Rat
1999-04-21 0:08 ` Hrvoje Niksic
1999-04-22 7:52 ` Can't read this! " Jaap-Henk Hoepman
1999-04-22 9:09 ` Lee Willis
1999-04-23 14:50 ` Justin Sheehy
1999-04-21 7:26 ` Writing enriched text Kai.Grossjohann
1999-04-21 12:48 ` William M. Perry
1999-04-21 13:43 ` Laura Conrad
1999-04-21 13:45 ` Kai.Grossjohann
1999-04-21 15:03 ` Alan Shutko
1999-04-21 17:29 ` Oscar Figueiredo
1999-04-21 17:51 ` William M. Perry
1999-04-22 15:01 ` Kai.Grossjohann
1999-04-23 20:39 ` François Pinard
1999-04-25 18:17 ` Hrvoje Niksic
1999-04-25 21:34 ` Kai.Grossjohann
1999-04-21 19:08 ` Lars Magne Ingebrigtsen
1999-04-21 21:41 ` Hrvoje Niksic
1999-04-22 7:24 ` Colin Marquardt
1999-04-22 8:41 ` Hrvoje Niksic
1999-04-22 15:37 ` Jan Vroonhof
[not found] ` <k8z <byiuaohdim.fsf@bolzano.math.ethz.ch>
1999-04-23 7:42 ` Colin Marquardt
1999-04-23 20:44 ` François Pinard
1999-04-25 18:14 ` Hrvoje Niksic
[not found] ` <knn202ks3v.fsf@concord.com>
1999-04-21 14:22 ` William M. Perry [this message]
1999-04-24 15:17 ` François Pinard
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=86676q6ol0.fsf@kramer.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).