From: Steinar Bang <sb@metis.no>
Subject: Re: IMAP + MIME + pGnus...
Date: 21 Apr 1999 09:33:06 +0200 [thread overview]
Message-ID: <whr9pebf7x.fsf@viffer.oslo.metis.no> (raw)
In-Reply-To: Simon Josefsson's message of "20 Apr 1999 16:50:46 +0200"
>>>>> Simon Josefsson <jas@pdc.kth.se>:
> Yup. Another approach would be to make Gnus aware of MIME-capable
> backends, ie a backend function that fetched the MIME structure of the
> article, and then fetch the parts it want to display.
> I'm not sure which approach create the least amount of trouble with
> all caching stuff. OTOH I think the second approach is much closer to
> the Right Thing, so perhaps one should try that first.
I agree. My vote goes to the MIME-aware backend.
next prev parent reply other threads:[~1999-04-21 7:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-20 14:35 William M. Perry
1999-04-20 14:50 ` Simon Josefsson
1999-04-21 7:33 ` Steinar Bang [this message]
1999-04-23 15:47 ` William M. Perry
1999-06-12 2:26 ` Lars Magne Ingebrigtsen
1999-04-21 7:32 ` Steinar Bang
1999-04-21 7:43 ` Kai.Grossjohann
1999-04-22 12:59 ` Steinar Bang
1999-04-22 14:59 ` Kai.Grossjohann
1999-04-22 15:51 ` Simon Josefsson
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=whr9pebf7x.fsf@viffer.oslo.metis.no \
--to=sb@metis.no \
/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).