Gnus development mailing list
 help / color / mirror / Atom feed
From: Sean Doran <smd@ebone.net>
Subject: Re: !MML
Date: Sun, 15 Nov 1998 18:27:43 +0100 (CET)	[thread overview]
Message-ID: <199811151727.SAA02236@sean.ebone.net> (raw)

Kai wrote:

| I think if you want to go the route of marking up MIME stuff with
| normal text (as opposed to text properties), then the markup should be
| something which is unlikely to occur in the normal mail text.
|
| Parentheses and SGML-like tags are too likely to occur in normal mail
| text, IMHO.

I think the point was to have an actual language for describing
MIME messages that would be amenable to automation, rather than
to have something specifically designed to be especially user-friendly.

Something Lisp-like seemed pretty natural since Gnus developers
seem pretty fluent in Lisp.

Also, Lisp is not especially user-unfriendly, so if someone who knows Lisp
had some reason to go munging the MIME message at the description-language
level, she or he would have a relatively small learning curve.

Normally keystroke mechanisms would be used to do the manipulation.

| What about saying that a line beginning with a special string is such
| a MIME markup?  Let's say lines beginning with "@.:" or something.
| (Don't use "@#$%", that'll be too often used for four-letter words :-)

Well, I guess APL is another strong candidate...

	Sean. (with mad visions of higher-order functions in Gnus-to-Gnus MIME)


             reply	other threads:[~1998-11-15 17:27 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-11-15 17:27 Sean Doran [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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-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     ` !MML Hrvoje Niksic
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

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=199811151727.SAA02236@sean.ebone.net \
    --to=smd@ebone.net \
    /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).