From: morioka@jaist.ac.jp (守岡 知彦 / MORIOKA Tomohiko)
Subject: Re: MIME message parts from backends (specifically IMAP)
Date: 10 Jan 1998 01:39:32 +0900 [thread overview]
Message-ID: <s1cd8i11u0r.fsf@mousai.jaist.ac.jp> (raw)
In-Reply-To: Steinar Bang's message of "05 Jan 1998 08:41:36 +0100"
>>>>> In <whvhvzs6z3.fsf@norne.oslo.metis.no>
>>>>> "Steinar" = Steinar Bang <sb@metis.no> wrote:
Steinar> How could you actually *do* something specifically IMAP'y?
Steinar> Gnus doesn't know about anything except the standard backend
Steinar> operations, does it?
I think IMAP'y MIME parser or data representation is good idea. I
would like to introduce external MIME parser to SEMI. mime-parse.el
should be rewrote to IMAP'y and should use IMAP as external parser.
If someone will start to define abstraction and implementation of
IMAP'y MIME handling, I would like to cooperate and use code in SEMI.
--
tomo.
prev parent reply other threads:[~1998-01-09 16:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-01 15:17 Steinar Bang
1998-01-04 9:55 ` Lars Magne Ingebrigtsen
1998-01-05 7:41 ` Steinar Bang
1998-01-06 6:35 ` Lars Magne Ingebrigtsen
1998-01-06 16:50 ` Steinar Bang
1998-01-09 16:39 ` 守岡 知彦 / MORIOKA Tomohiko [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=s1cd8i11u0r.fsf@mousai.jaist.ac.jp \
--to=morioka@jaist.ac.jp \
/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).