From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: mm-w3m-cid-retrieve-1 -> mm-handle-media-supertype called with nil arg
Date: Mon, 06 Mar 2006 14:56:54 +0100 [thread overview]
Message-ID: <v93bhvfzh5.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <b4m8xroysgh.fsf@jpl.org>
On Mon, Mar 06 2006, Katsumi Yamaoka wrote:
> Thank you for analyzing the bug. It might happen with broken
> articles even in usual groups. I've fixed it so as not to cause
> an error,
Confirmed. Thanks.
> instead of searching the other articles in the digest group for the
> related part.
This doesn't work when I select <2.1 html> (the image is <2.2 png>
inside <2.* related>) in the example I gave. Thinking more about it,
I think it is a pilot error: I should probably pick <2.* related> if I
want to see the image. Maybe checking other parts isn't necessary.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
prev parent reply other threads:[~2006-03-06 13:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <v94q2jmhab.fsf@marauder.physik.uni-ulm.de>
2006-03-03 15:23 ` Reiner Steib
2006-03-06 6:53 ` Katsumi Yamaoka
2006-03-06 13:56 ` Reiner Steib [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=v93bhvfzh5.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
/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).