X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: "Cary Jamison" Subject: Re: CR/LF problems after upgrade Date: Wed, 17 Jan 2007 10:35:41 -0700 Lines: 34 Message-ID: References: <20070112055257 DOT 55D3083C6F AT pessard DOT research DOT canon DOT com DOT au> <31DDB7BE4BF41D4888D41709C476B6570416963D AT NIHCESMLBX5 DOT nih DOT gov> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Buchbinder, Barry (NIH/NIAID) [E] wrote: > From: Luke Kendall >> >> I wonder how many centuries of human endeavour has been >> absorbed because of the decision to use CR+LF as line >> endings in DOS? >> > > > To be fair, \r\n seems to go back to Gary Kildall's CP/M. > http://en.wikipedia.org/wiki/Unprintable_characters > As far as I know, Unix is actually the oddball, using only a single character to represent two actions on the old ttys, a carriage return followed by a line feed. All oses I used before I was exposed to Unix had line endings - these included various other mini and microcomputer oses of the late 70s early 80s era. Note that it was important to send the carriage return *before* the line feed, to give the carriage head more time to actually return all the way to the start of the line. If you did the line feed before the carriage return, the next character after the carriage return could start printing while the carriage was still returning! (Actually, this is only true of really old style KSRs that didn't have much buffering, etc., but shows the history of \r\n.) And now that I'm way off topic, I'll just add that if anyone else wants to continue reminiscing, lets take it to -talk. Cary -- 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/