This is the mail archive of the
mailing list for the cygwin project.
Re: CR/LF problems after upgrade
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: The Cygwin-Talk Maiming List <cygwin-talk at cygwin dot com>
- Date: Wed, 17 Jan 2007 16:48:45 -0500
- Subject: Re: CR/LF problems after upgrade
- References: <20070112055257.55D3083C6F@pessard.research.canon.com.au> <31DDB7BE4BF41D4888D41709C476B6570416963D@NIHCESMLBX5.nih.gov> <email@example.com> <firstname.lastname@example.org> <20070117214739.GA18681@trixie.casa.cgf.cx>
- Reply-to: cygwin-talk at cygwin dot com
- Reply-to: The Cygwin-Talk Maiming List <cygwin-talk at cygwin dot com>
On Wed, Jan 17, 2007 at 04:47:39PM -0500, Christopher Faylor wrote:
>On Wed, Jan 17, 2007 at 12:47:12PM -0800, Shankar Unni wrote:
>>Cary Jamison wrote:
>>>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
>>><cr><lf> line endings - these included various other mini and
>>>microcomputer oses of the late 70s early 80s era.
>>Thank you, Methuselah!
>>Hey, on the old OSes that *I* used, there was no concept of a "line
>>separator". *Real* OSes used *records* (fixed-length space-padded, or
>>variable-length) for all files, including text files :-). <CR><LF> was
>>only used for formatting the file for printing..
>? The OSes that I used didn't need padding. I just stayed within 7
>characters and used a new card when I needed to move to the next "line".
>No need for a backup either, since my programs were all on convenient,
(stupid laptop drops keystrokes since I took it apart)