From: Theo Honohan <theoh@chiark.greenend.org.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Is there a list for Limbo/Inferno discussion?
Date: Fri, 29 Sep 2000 12:08:33 +0100 [thread overview]
Message-ID: <E13ey1p-0005O3-00@chiark.greenend.org.uk> (raw)
In-Reply-To: Your message of "Wed, 27 Sep 2000 11:09:47 +0200." <20000927110947.R26209@cackle.proxima.alt.za>
In message <20000927110947.R26209@cackle.proxima.alt.za>, Lucio De Re writes:
> On Wed, Sep 27, 2000 at 08:53:30AM +0000, forsyth@caldo.demon.co.uk wrote:
> >
> > i was originally hoping to stick to usenet for open inferno/limbo
> > discussion, because
[...]
>
> PS: Your lines have crawled back to beyond my margins :-)
>
I've been wondering whether some level of support for RFC 2646
"format=flowed" would be an appropriate addition to acme Mail.
Living among the fallen, I'm used to emacs's various adaptive and
automatic filling modes. I often end up using them (interactively) to
achieve the same wrapping effect as "format=flowed" in quoted text.
It's not really very satisfactory -- it's too easy to mangle the text.
"Format=flowed" seems to offer the possibility of safely automating
the bulk of this work, and it's becoming quite widely supported. I
would be interested to hear good or bad opinions about it from people
on the list.
(I suppose an alternative, in the UTF-8 mail world, would be to use
Unicode "line separator" as a soft line break. Unless you also put in
a CRLF at the end of each "line", though, you would run into problems
with the SMTP line length limit (and non-Unicode readers would get
even worse formatting.))
next prev parent reply other threads:[~2000-09-29 11:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-26 8:04 Skip Tavakkolian
2000-09-27 8:53 ` forsyth
2000-09-27 9:09 ` Lucio De Re
2000-09-29 11:08 ` Theo Honohan [this message]
2000-09-27 13:58 ` Doug NoNum Henderson
2000-09-27 10:21 okamoto
2000-09-28 8:42 forsyth
2000-09-29 8:31 ` Ralph Corderoy
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=E13ey1p-0005O3-00@chiark.greenend.org.uk \
--to=theoh@chiark.greenend.org.uk \
--cc=9fans@cse.psu.edu \
/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).