From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: ding@gnus.org
Subject: Re: flow-fill.el and rfc3676
Date: Sun, 16 Apr 2006 17:20:08 +0200 [thread overview]
Message-ID: <m3hd4t7djr.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <m3ekmcw9ro.fsf@pigpen.waxrat.com> (Michael Cook's message of "Thu, 12 Aug 2004 13:23:23 -0400")
Michael Cook <michael@waxrat.com> writes:
> flow-fill.el implements rfc2646. rfc2646 has been obsoleted by
> rfc3676. i think the only interesting change is the addition of the
> delsp=yes modifier.
>
> anybody feel like updating flow-fill.el to implement delsp=yes?
Sure. Could you forward a message that uses delsp?
(Perhaps we should have a Gnus newsgroup/mailing list/whatever that
has a repository of interesting MIME (and otherwise) documents. A
corpus of test subjects. It might have to be categorised in some
handy way to be useful, though...)
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2006-04-16 15:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 17:23 Michael Cook
2006-04-16 15:20 ` Lars Magne Ingebrigtsen [this message]
2006-04-17 2:29 ` Michael Cook
2006-04-17 9:11 ` Lars Magne Ingebrigtsen
2006-04-17 15:43 ` Michael Cook
2006-04-18 16:52 ` Lars Magne Ingebrigtsen
2006-04-18 8:45 ` Simon Josefsson
2006-04-18 16:31 ` 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=m3hd4t7djr.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=ding@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).