From: "John Cooper (UK)" <john.cooper@eu.citrix.com>
Subject: Re: Mailcap problem specifying application/octet-stream
Date: 16 Aug 2000 15:50:01 +0100 [thread overview]
Message-ID: <ud7j9dzvq.fsf@KONTIKI.cam.eu.citrix.com> (raw)
In-Reply-To: ShengHuo ZHU's message of "15 Aug 2000 13:30:28 -0400"
ShengHuo ZHU <zsh@cs.rochester.edu> writes:
> Toby Speight <streapadair@gmx.net> writes:
>
> > Perhaps Lisp functions take precedence over shell commands in
> > mm-mailcap-data?
>
> It's the truth.
>
> > Is that the case? If so, is there a way to override it?
>
> Remove the lisp function entry or redefine mailcap-viewer-lessp.
Thanks for the clarification.
The following (in my .gnus) removes the default application/octet-stream entry,
thus allowing my .mailcap specification to take effect:
(require 'mailcap)
(let* ((application (assoc "application" mailcap-mime-data))
(octet-stream (assoc "octet-stream" application)))
(when (symbolp (cdr (assoc 'viewer octet-stream)))
(delete octet-stream application)))
--- John
prev parent reply other threads:[~2000-08-16 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-15 15:20 John S Cooper
2000-08-15 17:19 ` Toby Speight
2000-08-15 17:30 ` ShengHuo ZHU
2000-08-16 14:50 ` John Cooper (UK) [this message]
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=ud7j9dzvq.fsf@KONTIKI.cam.eu.citrix.com \
--to=john.cooper@eu.citrix.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).