Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!wuarchive!kuhub.cc.ukans.edu!2fhddowel
From: 2FHDDOWEL@kuhub.cc.ukans.edu
Newsgroups: comp.sys.amiga.tech
Subject: Re: LF vs CR LF
Message-ID: <10655@kuhub.cc.ukans.edu>
Date: 5 Sep 89 21:32:22 GMT
References: <8908250325.AA28433@postgres.Berkeley.EDU>
Organization: University of Kansas Academic Computing Services
Lines: 25

In article <8908250325.AA28433@postgres.Berkeley.EDU>, dillon@POSTGRES.BERKELEY.EDU (Matt Dillon) writes:
> :How about using CR LF's?  One seriously braindamaged (in my opInion) 'feature'
> :of AmigashmnOS is that it uses LF's for end of lines.  This creates lots
> :of problems when I'm taking my textfiles to IBM's and other machines.
> :
> :Why couldn't they have done it proper? Lf is a line feed! and CR is a
> :carriage return.  It's a pain when programs start sticking out LF's
> :in the middle of lines.  Such programs usualy crap out on my terminal
> :(he who lives without a terminal for editing is not alive).
> 
> 	HA!  That really strikes me funny.  Do you know what kind of @!#$
>     crap one has to go through with 'cooked' and 'raw' modes on IBM (pc)
>     files?  Yes, that's right, on file descriptors, implemented at the
>     DOS level.  It screws up everything.  Do you know that the default for
>     IBM-PC *DEVICE DRIVERS* is 'cooked' ??  You need to do an ioctl to fix
>     it.
> 
> 	CR LF is an old standard ... very very very old.  LF alone has 
>     been around for many many years and is the new standard.  It is much
>     easier to deal with a single line terminator character than a pair.
> 
> 	In anycase, your 'pain' probably comes from your upbringing.  I
>     use mainly UNIX boxes which all use a single LF as a line terminator.
> 
> 					-Matt