delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2004/07/09/06:39:30

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
Message-ID: <40EE7656.909036FE@dessent.net>
Date: Fri, 09 Jul 2004 03:41:26 -0700
From: Brian Dessent <brian AT dessent DOT net>
Organization: My own little world...
MIME-Version: 1.0
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?")
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> <004701c46597$e9040b80$4e6510ac AT ds DOT tao DOT co DOT uk>
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

William Blunn wrote:

> I believe that at this point they are talking about the byte stream that
> represents the encoded form of the message.
> 
> If you are using quoted-printable encoding, then all encoded lines will
> be 78 characters or less, and so will be fitting in with the "SHOULD"
> specification, i.e. the most conformant.

Right, I understand that as well.

> And what problems would there be with that flowed message in other
> environments?
> 
> Every mail reader I have ever seen wraps lines.
> 
> Every web browser I have ever seen wraps lines.  The only problem here
> is that most archiving software rather unhelpfully mandates that the
> browser must not wrap at the right edge of the viewer's window.

My main problem with it is that it breaks quoting.  When I reply to a
message with no line breaks, my mail program has to either A) pick an
arbitrary margin and reflow the entire message to that margin, adding
">" to the first column of each line, or B) Insert a ">" at the
beginning of the paragraph and just let the long line dangle.  To the
person reading it will not appear correctly quoted (depending on screen
width) because only the first line will have a ">" prepended.  If you
have color highlighting enabled then this is even more apparent.  Option
(A) is leads to the conclusion that having the original message with
line breaks inserted is the best way to go if you expect it to be quoted
as part of a discussion, since that's the format it's going to end up in
for every message in the thread except the original post.  Option (B)
just results in broken quoting, and therefore should be avoided.

> > It's just like HTML email - can I read it?  Yes.  Do I want it in my
> > inbox? Heck no.
> 
> I don't think this is valid.

It's valid in that I can view messages with long lines just fine, I just
don't  like them -- because I'm used to <80 column margins, they read
better on my screen, and I believe that email works better that way. 
This is not a technical statement but rather an opinion.  Likewise I CAN
view HTML emails but I hate receiving them because they come festered
with all sorts of colors and fonts.  (There are further technical
reasons why HTML email is stupid, so in that sense it is more valid than
a simple statement of opinion.)

Brian

--
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 -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019