From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: [0.91, bug?] Handles image/gif improper
Date: 11 Jul 1999 11:17:03 +0200 [thread overview]
Message-ID: <m3908nv94g.fsf@quimbies.gnus.org> (raw)
In-Reply-To: Jonas Steverud's message of "10 Jul 1999 10:55:42 +0200"
Jonas Steverud <d4jonas@dtek.chalmers.se> writes:
> Yes looks like it, but 0.84 obvious did not... What did that do? Did
> it have some variable or what file did it read? I'm curious why 0.84
> worked while 0.91 did not. Hmmm...
The mailcap parsing has been improved.
> > If you don't want it to take this action, then you should put
> > something else in your ~/.mailcap, I guess...
>
> I'll do that. But I prefer the lisp-way... ;-)
You can add rules with `mailcap-add'.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1999-07-11 9:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <wtniu7tr4lj.fsf@leemor.dtek.chalmers.se>
1999-07-09 21:08 ` Lars Magne Ingebrigtsen
[not found] ` <wtnemigg9yp.fsf@licia.dtek.chalmers.se>
1999-07-11 9:17 ` Lars Magne Ingebrigtsen [this message]
[not found] ` <wtniu7rqeh7.fsf@licia.dtek.chalmers.se>
1999-08-27 17:25 ` 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=m3908nv94g.fsf@quimbies.gnus.org \
--to=larsi@gnus.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).