This is the mail archive of the cygwin-talk mailing list for the cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: CR/LF problems after upgrade

Christopher Faylor wrote:
> 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..

Heh, and you're calling me Methuselah??

>> ?  The OSes that I used didn't need padding.  I just stayed within 7
>                                                                    72
>> 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, flammable cards.
> (stupid laptop drops keystrokes since I took it apart)
> cgf

I was wondering how you fit much on a 7 character line!

Of course, the real, state-of-the art oses I used could emulate the older 
record based ones.  But, once you moved to a time-share system with multiple 
terminals, who wanted fixed-length lines?


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]