Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Purdy boundary
Date: 18 Nov 1998 03:52:49 +0100	[thread overview]
Message-ID: <m3af1psoe6.fsf@sparky.gnus.org> (raw)

I think it's important that the multipart boundary be as pretty as
possible.  I'm using


--=-=-=

as the default boundary, and am adding one "=" for each subsequent
(and/or nested) multipart, so we get

--=-=-=
--==-=-=
--===-=-=
--====-=-=

and so on.  (This doesn't work properly in 0.49.)

In 0.50 I've added checks for whether this boundary is unique, and if
it's not, it iterates until it finds a unique boundary.

But is this the prettiest possible boundary?  The two hypens at the
beginning are outside our control, but the rest we can do what we want 
with.  It has to be less than 70 characters long, though.

The concluding boundary has two hypens at the end.  Like this:

--=-=-=--

Hey!  Symmetrical!  Neat!

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@ifi.uio.no * Lars Magne Ingebrigtsen


             reply	other threads:[~1998-11-18  2:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-11-18  2:52 Lars Magne Ingebrigtsen [this message]
1998-11-18 11:02 ` Didier Verna
1998-11-18 12:02   ` luis fernandes
1998-11-18 12:55     ` Steinar Bang
1998-11-18 13:28       ` Lars Magne Ingebrigtsen
1998-11-18 11:51 ` Fredrik Glöckner
1998-11-18 13:17   ` Lars Magne Ingebrigtsen
1998-11-18 20:21   ` George J McNinch
1998-11-19  2:09     ` Lars Magne Ingebrigtsen
1998-11-19  9:28     ` Fredrik Glöckner
1998-11-20  2:07       ` Lars Magne Ingebrigtsen
     [not found] ` <6faf1p9nbv.fsf@dna.lth.se>
1998-11-18 13:24   ` Lars Magne Ingebrigtsen
     [not found]     ` <6f7lwt9lah.fsf@dna.lth.se>
1998-11-18 13:53       ` Lars Magne Ingebrigtsen
1998-11-18 18:16 ` Wes Hardaker
1998-11-19  2:08   ` 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=m3af1psoe6.fsf@sparky.gnus.org \
    --to=larsi@ifi.uio.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).