From: Reiner Steib <reinersteib+gmane@imap.cc>
To: info-gnus-english@gnu.org
Subject: Re: handling other mime types
Date: Sat, 31 Mar 2007 11:33:57 +0200 [thread overview]
Message-ID: <v9tzw1u58a.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87d52r9h2m.fsf@gmail.com>
On Fri, Mar 30 2007, Hadron wrote:
> k|b|s <see@my.sig.invalid> writes:
>> In ~/.mailcap
>>
>> video/*; /path/to/mplayer %s
>
> Hi,
>
> I followed this advice, but Gnus still prompts me to save the file.
Did you restart Gnus (and Emacs) after the change?
Does `M-x mailcap-parse-mailcaps RET' help?
See ` <f1> f mailcap-parse-mailcaps RET' and (info
"(emacs-mime)mailcap") for more information.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2007-03-31 9:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-29 8:33 Hadron
[not found] ` <m2fy7oxwnc.fsf@my.sig.invalid>
2007-03-30 10:11 ` Hadron
2007-03-31 9:33 ` Reiner Steib [this message]
2007-04-01 12:14 ` Hadron
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=v9tzw1u58a.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=info-gnus-english@gnu.org \
/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).