From: Jesper Harder <harder@myrealbox.com>
Subject: Re: Disable mailcap support
Date: Fri, 03 Oct 2003 00:25:55 +0200 [thread overview]
Message-ID: <m3y8w3qnt8.fsf@defun.localdomain> (raw)
In-Reply-To: <v9ad8jqzzx.fsf@marauder.physik.uni-ulm.de>
Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:
> On Wed, Oct 01 2003, Jesper Harder wrote:
>
>> I think I agree. But I don't understand why there are external
>> viewers in `mailcap-mime-data' in the first place.
>
> It seems (from the ChangeLog entries for `mailcap-mime-data') that
> most entries are quite old.
mailcap.el is originally from w3 -- I think those entries were already
there when it was imported to Gnus.
> (Just a thought...) We could split the data as follows:
> - defcustom mailcap-mime-data-internal (Lisp, PGP, message/* and other
> internal stuff?)
> - defvar mailcap-mime-data-external (build this from mailcap files)
> - defvar mailcap-mime-data-external-fallback
>
> The default should be mailcap-mime-data = mailcap-mime-data-internal +
> mailcap-mime-data-external. The user should be able to add the
> fallback entries `mailcap-mime-data-external-fallback' with, say
> (mailcap-add-fallback).
I'm not sure I get the purpose of the fallback entries. What is the
difference between `mailcap-add' and `mailcap-add-fallback'?
next prev parent reply other threads:[~2003-10-02 22:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-28 16:11 Florian Weimer
2003-09-28 22:56 ` Jesper Harder
2003-09-29 18:04 ` Florian Weimer
2003-09-29 21:47 ` Jesper Harder
2003-11-09 15:35 ` Florian Weimer
2004-01-03 19:28 ` Reiner Steib
2003-09-29 19:35 ` Reiner Steib
2003-09-29 21:27 ` Jesper Harder
2003-09-30 18:04 ` Reiner Steib
2003-09-30 23:37 ` Jesper Harder
2003-10-02 18:02 ` Reiner Steib
2003-10-02 22:25 ` Jesper Harder [this message]
2003-10-03 18:10 ` Reiner Steib
2003-10-17 17:17 ` Lars Magne Ingebrigtsen
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=m3y8w3qnt8.fsf@defun.localdomain \
--to=harder@myrealbox.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).