From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: More On Mime
Date: 12 Feb 1998 11:25:27 +0100 [thread overview]
Message-ID: <rjhg655dd4.fsf@zuse.+dina.kvl.dk> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 11 Feb 1998 14:42:29 +0100
Nice. I have been thinking about it from a customization point of
view, i.e. how to specify methods for handling each content-type.
emime-standard-methods
General methods provided by the mime library
emime-mailcap-methods
General methods parsed from the mailcap file
emime-user-methods (customizable)
General methods specified by the user.
emime-aplication-standard-methods
Extra methods specified by the application (i.e. Gnus, W3, RMAIL).
emime-application-user-methods
Extra methods specified by the user for this application only.
When the mime library want to handle a particular content type, it
should look through all the above. The latest taking priority.
The individual applications would bind
`emime-aplication-standard-methods' and
`emime-application-user-methods' before calling the library. E.g.
(let ((emime-aplication-standard-methods gnus-emime-standard-methods)
(emime-application-user-methods gnus-emime-user-methods))
(emime-handle handle))
Maybe there should be separate variable for internal and external
display of content.
Maybe the priority of the mailcap methods have to be more detailed
than the above. I believe you can specify application specific
methods in mailcap as well.
next prev parent reply other threads:[~1998-02-12 10:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-10 19:56 Lars Magne Ingebrigtsen
1998-02-11 9:10 ` Steinar Bang
1998-02-11 13:34 ` Lars Magne Ingebrigtsen
1998-02-11 20:21 ` François Pinard
1998-02-11 21:29 ` SL Baur
1998-02-12 7:54 ` Steinar Bang
1998-02-12 8:13 ` SL Baur
1998-02-13 2:14 ` Matt Armstrong
1998-02-13 11:19 ` Lars Magne Ingebrigtsen
1998-02-13 12:15 ` SL Baur
1998-02-13 16:04 ` William M. Perry
1998-02-13 17:07 ` Lars Magne Ingebrigtsen
1998-02-13 23:45 ` SL Baur
1998-02-11 10:05 ` Per Abrahamsen
1998-02-11 13:42 ` Lars Magne Ingebrigtsen
1998-02-11 13:57 ` Lars Balker Rasmussen
1998-02-13 11:18 ` Lars Magne Ingebrigtsen
1998-02-11 17:48 ` Wes Hardaker
1998-02-12 10:26 ` Per Abrahamsen
1998-02-12 20:18 ` Wes Hardaker
1998-02-11 20:31 ` François Pinard
1998-02-13 11:21 ` Lars Magne Ingebrigtsen
1998-02-12 10:25 ` Per Abrahamsen [this message]
1998-02-13 11:59 ` Lars Magne Ingebrigtsen
1998-02-12 21:12 ` Justin Sheehy
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=rjhg655dd4.fsf@zuse.+dina.kvl.dk \
--to=abraham@dina.kvl.dk \
/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).