fred smith:
|On Tue, Jan 26, 1999 at 06:29:50AM -0500, Randall Hopper wrote:
|> Daniel González Gasull:
|> |Randall Hopper:
|> |> I wonder if anyone has cooked a method to compose and send
|> |> text/enriched messages with Mutt.
|> |
|> |I'm not doing this, but the process would be something
|> |like:
|> ...
|> | plain2enriched is supossed to be a script that
|> | converts text/plain to text/enriched.
|>
|> I'd be more interested in a WYSIWYG interface where bold is bold, etc.
|> Such as is offered in GNU Emacs. It'd be helpful occasionally when
|> swapping mail with other users I know use mutt to use a bold or underline
|> now and again.
|
|Not having done it, I'll jump in here to say it could PROBABLY be done
|with editors (such as Elvis) which offer a "syntax coloring" capability,
|by building a custom "enriched" mode for the syntax highlighting description.
|If someone does it, I'd like to see it, though!
Emacs already has this as well. Just wondering if the sufficient bits have
yet been added to Mutt to make this integration somewhat seemless. For
example, being able to set through send-hooks whether "editor" should
generate text/plain or text/enriched, setting the MIME type of the
generated message body automatically to that configured MIME type without
'macro^T^Utext/...' tricks, etc.
For example, it would be really useful if this worked:
send-hook ~A "set editor_mime_type=text/plain"
send-hook [EMAIL PROTECTED] "set editor_mime_type=text/enriched"
set editor = "editor_wrapper %t %s"
where "%t" is the MIME type, like with other Mutt system commands. Here
editor_wrapper queues off $1 (%t) being text/plain or text/enriched to "do
the right thing" for editing plain text or enriched text with that your
favorite editor.
What do you think?
--
Randall Hopper
[EMAIL PROTECTED]
