From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: CID (Was Re: Those MIME requirements)
Date: 12 Sep 1998 13:53:41 +0200 [thread overview]
Message-ID: <m3zpc5mtru.fsf@sparky.gnus.org> (raw)
In-Reply-To: Jean-Yves Perrier's message of "12 Sep 1998 11:48:18 +0200"
Jean-Yves Perrier <perrier@nagra-kudelski.ch> writes:
> CID are more widely used in multipart/related messages (see RFC 2112).
I see. Well, I think I'll wait a bit with multipart/related.
> In order to be able to be able to write type handlers for such types, it
> would be greatly useful that Gnus provides a non-interactive like this:
>
> (gnus-give-message-part content-id).
I'm not sure I follow you...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1998-09-12 11:53 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-11 11:35 Those MIME requirements Lars Magne Ingebrigtsen
1998-09-11 12:51 ` Kai Grossjohann
1998-09-11 13:05 ` Steinar Bang
1998-09-11 14:23 ` Kai Grossjohann
1998-09-11 14:50 ` Steinar Bang
1998-09-11 15:08 ` Lars Magne Ingebrigtsen
1998-09-11 17:07 ` Jason L Tibbitts III
1998-09-11 21:10 ` Kai Grossjohann
1998-09-12 3:10 ` Lars Magne Ingebrigtsen
1998-09-12 8:47 ` Hrvoje Niksic
1998-09-12 11:41 ` Lars Magne Ingebrigtsen
1998-09-16 13:13 ` Hrvoje Niksic
1998-09-16 14:21 ` Lars Magne Ingebrigtsen
1998-09-17 12:07 ` Hrvoje Niksic
1998-09-11 21:06 ` Kai Grossjohann
1998-09-12 6:16 ` Lars Magne Ingebrigtsen
1998-09-11 13:48 ` Kai Grossjohann
1998-09-11 13:51 ` Kai Grossjohann
1998-09-11 15:12 ` Lars Magne Ingebrigtsen
1998-09-11 15:25 ` Hrvoje Niksic
1998-09-11 15:52 ` Lars Magne Ingebrigtsen
1998-09-11 18:10 ` Hrvoje Niksic
1998-09-11 19:16 ` William M. Perry
1998-09-11 20:25 ` Alan Shutko
1998-09-11 20:40 ` Richard Coleman
1998-09-13 1:59 ` William M. Perry
1998-09-12 6:10 ` Lars Magne Ingebrigtsen
1998-09-11 15:34 ` HTML (was: Re: Those MIME requirements) Per Abrahamsen
1998-09-11 17:26 ` William M. Perry
1998-09-11 18:12 ` Per Abrahamsen
1998-09-11 19:17 ` William M. Perry
1998-09-12 4:51 ` Lars Magne Ingebrigtsen
1998-09-12 9:58 ` Per Abrahamsen
1998-09-12 12:00 ` Lars Magne Ingebrigtsen
1998-09-13 1:41 ` William M. Perry
1998-09-13 6:57 ` Lars Magne Ingebrigtsen
1998-09-14 11:32 ` Per Abrahamsen
1998-09-14 14:00 ` Lars Magne Ingebrigtsen
1998-09-14 11:32 ` Per Abrahamsen
1998-09-14 8:56 ` Jan Vroonhof
1998-09-14 10:59 ` Dave Love
1998-09-14 11:32 ` Per Abrahamsen
1998-09-16 7:53 ` Hrvoje Niksic
1998-09-11 16:38 ` Those MIME requirements Hallvard B Furuseth
1998-09-12 2:56 ` Lars Magne Ingebrigtsen
1998-09-13 1:34 ` William M. Perry
1998-09-11 21:04 ` Kai Grossjohann
1998-09-12 6:15 ` Lars Magne Ingebrigtsen
1998-09-12 10:06 ` Lisp in mailcap file (Re: Those MIME requirements) Jean-Yves Perrier
1998-09-13 1:32 ` Those MIME requirements William M. Perry
1998-09-12 9:48 ` CID (Was Re: Those MIME requirements) Jean-Yves Perrier
1998-09-12 11:53 ` Lars Magne Ingebrigtsen [this message]
1998-09-13 1:37 ` William M. Perry
1998-09-13 6:08 ` Lars Magne Ingebrigtsen
1998-09-14 17:16 ` Those updated MIME requirements Steinar Bang
1998-09-15 0:43 ` Those " Simon Josefsson
1998-09-16 9:23 ` Lars Magne Ingebrigtsen
1998-09-16 13:10 ` Hrvoje Niksic
1998-09-16 15:06 ` Per Abrahamsen
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=m3zpc5mtru.fsf@sparky.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).