Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Thu, 8 Jul 2004 20:15:17 -0500
From:	Eduardo Chappa <chappa AT math DOT washington DOT edu>
To:	cygwin AT cygwin DOT com
Subject:	Re: Wrapping long lines (Was Re: FAQ update suggestion for "I'm having basic problems with find. Why?")
In-Reply-To:	<40EDEF6B.A5A5F06@dessent.net>
Message-ID:	<Pine.CYG.4.58.0407082005200.1064@edocomputer>
References:	<010701c464f4$398e2030$4e6510ac AT ds DOT tao DOT co DOT uk> <Pine DOT GSO DOT 4 DOT 58 DOT 0407081027371 DOT 11665 AT slinky DOT cs DOT nyu DOT edu> <013301c464fe$e2e425d0$4e6510ac AT ds DOT tao DOT co DOT uk> <Pine DOT GSO DOT 4 DOT 58 DOT 0407081124080 DOT 11665 AT slinky DOT cs DOT nyu DOT edu> <Pine DOT CYG DOT 4 DOT 58 DOT 0407081405270 DOT 1032 AT edocomputer> <Pine DOT GSO DOT 4 DOT 58 DOT 0407081549530 DOT 2377 AT slinky DOT cs DOT nyu DOT edu> <Pine DOT CYG DOT 4 DOT 58 DOT 0407081504350 DOT 1032 AT edocomputer> <40EDEF6B DOT A5A5F06 AT dessent DOT net>
MIME-Version:	1.0
X-IsSubscribed:	yes

On Thu, 8 Jul 2004, Brian Dessent wrote:

:) > We may agree or disagree about format=flowed sent to this list, but
:) > we have to agree that what was sent was an e-mail message, perfectly
:) > valid e-mail message to a mailing list and not a web page to a web
:) > site.
:)
:) RFC2822 (which obsoletes the old RFC822) states in section 2.2.1:
:)
:) There are two limits that this standard places on the number of
:) characters in a line. Each line of characters MUST be no more than 998
:) characters, and SHOULD be no more than 78 characters, excluding the
:) CRLF.

Yes, I read that, a long time ago, but that means that "it is recommended
that a client sends lines with less that 78 characters, and if you do send
one with more than 78 characters, e.g. 444, you are still in compliance of
the RFC".  That's what the word SHOULD means in that RFC.

:) Wrapping lines at less than 80 characters is the standard accepted way
:) of sending text email.

I do no disagree with you. In fact I do all the time.

:)  It's the least common denominator that's guaranteed to work
:) everywhere.

Not in my PDA. You see, today we have screens that are less than 80
characters wide, and that's the reason why we have flowed format.

:)  It's just like HTML email - can I read it?  Yes.  Do I want it in my
:) inbox?  Heck no.  Just because you can do something doesn't mean you
:) should.

Yes, you should read the definition of SHOULD in an RFC, did you do it,
no. Next time look for a better argument to support your point.

-- 
Eduardo
http://www.math.washington.edu/~chappa/pine/

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -