Gnus development mailing list
 help / color / mirror / Atom feed
From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: !MML
Date: 14 Nov 1998 21:52:02 +0100	[thread overview]
Message-ID: <kigsofmuhe5.fsf@jagor.srce.hr> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "14 Nov 1998 21:44:39 +0100"

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> > > (part :type image/gif)
> > > (external "~/rms.gif")
> > > (end multipart)
> > 
> > Would any of this be visible to the user?
> 
> All of it.

This is disturbing to me, because I tend to mail/post lots of Lisp
code.

> would be a possibility, though...  Yes, the `end' things are totally
> unLispy.  So the multipart would be:
> 
> (multipart :type alternative
> (part :type text/plain
> This is plain text.)
> (part :type image/gif
> (external "~/rms.gif")))
> 
> Er.

Double er.  The problem with this is that `This is plain text.'
must not contain closed parentheses -- or its parens must be balanced, 
depending on how you implement it -- but both strike me as wrong.  Of
course, you could roll in your own parser, like in the case of SGML,
but it sounds yucky.

Again, perhaps it's just me and everyone else is ha-ha-happy about
these design ideas for multipart composition.

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
Personifiers Unite!  You have nothing to lose but Mr. Dignity!


  reply	other threads:[~1998-11-14 20:52 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-11-14 19:15 !MML Lars Magne Ingebrigtsen
1998-11-14 20:02 ` !MML Hrvoje Niksic
1998-11-14 20:44   ` !MML Lars Magne Ingebrigtsen
1998-11-14 20:52     ` Hrvoje Niksic [this message]
1998-11-14 21:55       ` !MML Lars Magne Ingebrigtsen
1998-11-14 21:26     ` !MML Bruce Stephens
1998-11-15  0:46       ` !MML Lars Magne Ingebrigtsen
1998-11-16 12:32         ` !MML Per Abrahamsen
1998-11-15 13:47 ` !MML Kai.Grossjohann
1998-11-15 19:20   ` !MML Lars Magne Ingebrigtsen
1998-11-15 20:30     ` !MML Vladimir Volovich
1998-11-15 20:48       ` !MML Lars Magne Ingebrigtsen
1998-11-15 21:28     ` !MML Hrvoje Niksic
1998-11-15 22:19       ` !MML Lars Magne Ingebrigtsen
1998-11-14 21:02 !MML Sean Doran
1998-11-14 21:40 ` !MML Hrvoje Niksic
1998-11-15  4:49   ` !MML Shenghuo ZHU
1998-11-15  5:03     ` !MML Shenghuo ZHU
1998-11-15 19:18       ` !MML Lars Magne Ingebrigtsen
1998-11-15 21:28         ` !MML Hrvoje Niksic
1998-11-15 21:58           ` !MML Lars Magne Ingebrigtsen
1998-11-15 17:27 !MML Sean Doran
1998-11-15 18:04 ` !MML Kai.Grossjohann
1998-11-15 19:23   ` !MML Lars Magne Ingebrigtsen
1998-11-15 19:42     ` !MML Kai.Grossjohann
1998-11-15 20:41       ` !MML Lars Magne Ingebrigtsen
1998-11-15 20:28     ` !MML Vladimir Volovich
1998-11-16  5:45       ` !MML Lars Magne Ingebrigtsen
1998-11-16  6:42   ` !MML Yair Friedman
1998-11-16  8:42     ` !MML Kai.Grossjohann
1998-11-16 14:50       ` !MML Lars Magne Ingebrigtsen
1998-11-16 15:03         ` !MML Yair Friedman
1998-11-16 16:12         ` !MML Kai.Grossjohann
1998-11-17  9:29           ` !MML Robert Bihlmeyer

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=kigsofmuhe5.fsf@jagor.srce.hr \
    --to=hniksic@srce.hr \
    /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).