delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2008/12/22/14:16:52

X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Mon, 22 Dec 2008 14:16:01 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Rationale for line-ending recommendation?
Message-ID: <20081222191601.GD23447@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <877i5wlwc3 DOT fsf AT mcbain DOT luannocracy DOT com> <20081219090531 DOT GV14886 AT trikaliotis DOT net> <EF7F2E5833CC4B5C8D8003C4A8F5DD7A AT DFW5RB41> <f60fe000812190730p63bb7d93o61e4f65a9613c5fb AT mail DOT gmail DOT com> <gigg57$af0$1 AT ger DOT gmane DOT org> <452D2288F0FE4F1898E686A227A022BD AT DFW5RB41> <20081219170214 DOT GX6830 AT calimero DOT vinschen DOT de> <84dde90812221112t38ead661k3c1bcb4e6ccd4f1 AT mail DOT gmail DOT com>
MIME-Version: 1.0
In-Reply-To: <84dde90812221112t38ead661k3c1bcb4e6ccd4f1@mail.gmail.com>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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
Note-from-DJ: This may be spam

On Mon, Dec 22, 2008 at 02:12:11PM -0500, Linus Hicks wrote:
>On Fri, Dec 19, 2008 at 12:02 PM, Corinna Vinschen wrote:
>>
>> Yeah, right, if this were in fact the 21st century, why would we ever
>> have to deal with a 30 year old, idiotic-from-the-start text file format
>> using two line ending chars?
>
>How quickly we forget...
>
>The first devices that had any understanding of this kind of data
>stream generated display characters through mechanical means - much
>like an old mechanical typewriter. These devices all had a carriage
>that moved left to right or right to left depending on whether you
>moved the paper or the print head while it struck an inked ribbon
>between a platen and character dies that supplied a limited and fixed
>set of characters.
>
>The people who designed these things obviously saw the carriage return
>as distinct from the linefeed. In fact, these devices had no capacity
>to buffer the input data stream and even at 300 baud, it took longer
>to return the carriage than the interval between characters. If you
>did not supply some non-printing characters in the data stream after
>the CR/LF sequence, it would print the next character about half way
>back to the beginning of the next line.
>
>If you sent only CR as line terminator, you got all lines printed on
>the same line and eventually ate a hole in the paper. If you sent only
>LF, the carriage would shortly reach the far right margin and print
>each line in one character position on separate lines.
>
>Early design decisions, however well considered, sometimes remain to
>encumber the future, often for reasons of compatibility. The
>constraints of available technology at the time of an innovation can
>play a crucial role in this process.

Ok, this discussion has teetered into off-topic territory, as it always
does.  Gary has already taken the discussion to the cygwin-talk list.

If anyone is compelled to provide more history lessons (whether it's past
history or future history), please use the cygwin-talk list.

cgf

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