From: Toby Speight <streapadair@gmx.net>
Subject: Re: Mailcap problem specifying application/octet-stream
Date: 15 Aug 2000 18:19:50 +0100 [thread overview]
Message-ID: <87lmxyjvbd.fsf@delivery.cam.eu.citrix.com> (raw)
In-Reply-To: John S Cooper's message of "15 Aug 2000 16:20:21 +0100"
0> In article <uvgx23616.fsf@KONTIKI.cam.eu.citrix.com>,
0> John S. Cooper <URL:mailto:John.Cooper@eu.citrix.com> ("John") wrote:
John> However, my mailcap-mime-data now has 2 entries for
John> application/octet-stream:
John>
John> My .mailcap stuff:
John>
John> ("octet-stream"
John> (viewer . "shelex %s")
John> (type . "application/octet-stream"))
John>
John> .. and the default:
John>
John> ("octet-stream"
John> (viewer . mailcap-save-binary-file)
John> (non-viewer . t)
John> (type . "application/octet-stream"))
John>
John> When I hit RET on the MIME button, it seems the default action
John> takes effect and I'm prompted to save the attachment to a file.
John>
John> It looks like mailcap-add-mailcap-entry might be keeping both
John> entries because the viewer is different in each case (although
John> this is something of a guess!).
John>
John> Any ideas on how I can make my .mailcap specification for
John> application/octet-stream override the default?
Perhaps Lisp functions take precedence over shell commands in
mm-mailcap-data?
Is that the case? If so, is there a way to override it?
next prev parent reply other threads:[~2000-08-15 17:19 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 [this message]
2000-08-15 17:30 ` ShengHuo ZHU
2000-08-16 14:50 ` John Cooper (UK)
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=87lmxyjvbd.fsf@delivery.cam.eu.citrix.com \
--to=streapadair@gmx.net \
/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).