From: Kees de Bruin <kees_de_bruin@tasking.com>
Subject: Re: Gnus and Emacs 20.3 and MIME
Date: Wed, 26 Aug 1998 15:02:18 +0200 (MET DST) [thread overview]
Message-ID: <13796.1882.133581.264050@kouvola.tasking.nl> (raw)
In-Reply-To: <kigiujgavw2.fsf@jagor.srce.hr>
Hrvoje Niksic writes:
> Kees de Bruin <kees_de_bruin@tasking.com> writes:
>
> > I only hear people talking about TM for handling MIME, but what
> > about the way MIME is handled in VM. Mainly because of the full
> > integration of the MIME support in VM, the user doesn't have to
> > configure anything at all and it still works as expected.
>
> True. I would recommend to Lars to look at VM's MIME support and see
> if he likes that. Implementing something similar (at least at the UI
> level) would be a *very* good start.
In a private discussion with Steinar Bang I promised to post a list of MIME
functions the VM mail reader supports. The VM mail reader has support for
MIME since version 6.xx and, as far as I know, in the current version of VM
(6.61) the following MIME capabilities are present (or at least used by
me):
MIME encoding:
- Attachments are possible with whatever encoding the user wants. Also,
based on the extension of the file, VM can guess the correct encoding to
use. No mailcap/mimetypes support.
- Encoding can be done using internal ELisp functions, or via external
programs.
- Sending multiple messages as a single MIME digest.
MIME decoding:
- The user can configure what MIME types should be displayed inline
(meaning that it is either displayed in a buffer or directly via an
external program).
- For non-inline MIME types buttons are generated the user can use to save
the MIME part to a file, or open it in some external viewer.
- Alternative display of MIME messages: plain text (no conversions), using
inline display, or all buttons.
- Handling of multipart messages (am I correct here, I never tried this).
- Decoding can be done using internal ELisp functions, or via external
programs.
- Handling of MIME digests.
I have probably missed some other MIME functions, but the above are the
things I use regularly. If there are other that use VM maybe they can
update the above list.
Greetings,
--
Kees de Bruin Software Engineer
---------------------------------------------------------------------------
E-mail: kees_de_bruin@tasking.com Tasking Software BV
Voice: +31-33-455 85 84 Plotterweg 31
Fax: +31-33-455 00 03 3821 BB Amersfoort
WWW: http://www.tasking.com The Netherlands
--[ In memory, everything seems to happen to music -- Tennessee Williams ]-
next prev parent reply other threads:[~1998-08-26 13:02 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-25 11:49 Kai Grossjohann
1998-08-25 14:21 ` François Pinard
1998-08-25 14:55 ` Jean-Yves Perrier
1998-08-25 18:06 ` Edward J. Sabol
1998-08-26 6:32 ` Steinar Bang
1998-08-26 18:35 ` SL Baur
1998-08-25 14:45 ` Steinar Bang
1998-08-25 15:39 ` Alan Shutko
1998-08-25 20:53 ` Andy Eskilsson
1998-08-25 15:48 ` Jan Vroonhof
1998-08-25 17:28 ` François Pinard
1998-08-25 17:58 ` Kai Grossjohann
1998-08-25 21:34 ` SL Baur
1998-08-25 21:59 ` Alan Shutko
1998-08-25 21:50 ` SL Baur
1998-08-25 22:05 ` Hrvoje Niksic
1998-08-25 23:01 ` Michael Harnois
1998-08-26 5:37 ` Kees de Bruin
1998-08-26 10:18 ` Hrvoje Niksic
1998-08-26 12:56 ` Steinar Bang
1998-08-26 13:02 ` Kees de Bruin [this message]
1998-08-26 13:18 ` Jake Colman
1998-08-26 13:25 ` Steinar Bang
1998-08-26 13:42 ` Jean-Yves Perrier
1998-08-26 13:36 ` Hrvoje Niksic
1998-08-26 13:56 ` Lars Magne Ingebrigtsen
1998-08-26 16:53 ` Hrvoje Niksic
1998-08-26 17:17 ` Lars Magne Ingebrigtsen
1998-08-26 17:27 ` Hrvoje Niksic
1998-08-26 18:34 ` Dave Love
1998-08-26 13:30 ` Steinar Bang
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=13796.1882.133581.264050@kouvola.tasking.nl \
--to=kees_de_bruin@tasking.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).