Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: Can gnus compose a html mail message?
Date: Wed, 12 Mar 2003 11:45:45 +0100	[thread overview]
Message-ID: <iluptown9ra.fsf@latte.josefsson.org> (raw)
In-Reply-To: <84wuj5s2bh.fsf@zsw.com> (Steven Woody's message of "Wed, 12 Mar 2003 11:15:14 +0800")

Steven Woody <steven@steven4u.net> writes:

> Simon Josefsson <jas@extundo.com> writes:
>
>> Steven Woody <steven@steven4u.net> writes:
>>
>>> ?
>>
>> Put <#part type=text/html> at the top of your message and then 
   type
>> ahead.
>>
> It works! thank you.  Where to find the manual about the <#part> 
  tag?
> I like to study all of it's properties, for example, I may want 
  to
> specify a charset, a tranfer encoding method, etc.

It is on the Emacs MIME manual, the section "Composing" should 
discuss all those things (if not, please send a bug report).

>> If you want WYSIWYG, I'm not so sure.  Emacs has support for 
   editing
>> enriched text (i.e., see $emacssrc/etc/enriched.doc), 
   converting that
>> into HTML shouldn't be too hard, and seems to be on the todo 
   list for
>> enriched.el.  There was a package that generated HTML based on
>> font-lock markup, perhaps using it in a enriched text buffer 
   works.
>
> I found the enrich-mode is very hard to use :-(

I agree.  Mostly because it lacks a toolbar with markup commands, 
like most WYSIWYG editors do.




  reply	other threads:[~2003-03-12 10:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-11 12:58 Steven Woody
2003-03-11 13:21 ` Jesper Harder
2003-03-11 16:57 ` Zack Weinberg
2003-03-11 17:54 ` Simon Josefsson
2003-03-12  3:15   ` Steven Woody
2003-03-12 10:45     ` Simon Josefsson [this message]
2003-03-11 21:32 ` Xavier MAILLARD
2003-03-12  3:16   ` Steven Woody
2003-03-12  3:57     ` Zack Weinberg

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=iluptown9ra.fsf@latte.josefsson.org \
    --to=jas@extundo.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).