Path: utzoo!utgpu!watmath!iuvax!rutgers!usc!pollux.usc.edu!addison
From: addison@pollux.usc.edu (Richard Addison)
Newsgroups: comp.sys.amiga.tech
Subject: Re: DME and vanishing text
Summary: What?  AmigaDOS does a UNIX thing?
Keywords: Newlines
Message-ID: <19148@usc.edu>
Date: 12 Aug 89 21:29:17 GMT
References: <89222.135727WTW101@PSUVM> <15874@watdragon.waterloo.edu>
Reply-To: addison@pollux.usc.edu (Richard Addison)
Distribution: comp.sys.amiga.tech
Organization: University of Southern California, Los Angeles, CA
Lines: 28

In article <15874@watdragon.waterloo.edu> rtczegledi@crocus.waterloo.edu (Richard Czegledi) writes:
}In article <89222.135727WTW101@PSUVM> WTW101@PSUVM.BITNET (Bill Warner) writes:
}>I am outputing text in assembly using the DOS funtion Write(...).    I am
}>terminating my lines with single linefeeds.  The text outputs to the default
}>output device (the screen) just fine.   When I redirect my text to the disk
}>The missing text occurs when I continue a line of text.  i.e.  I call
}[...]
}>Write(...) and print some text, then I call Write(...) again and print text
}>thats terminates with a linefeed.   The latter half of the text dissapears!
}
}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).

Interestingly enough (considering the alleged bias of the creators of AmigaDOS),
this is a convention from UNIX.  Having a single character to mark an end of
line is rather handy, actually.

DME will show the CR characters as reversed M's (at least when I use WB1.3's
NEWCON:).

Richard Addison
"The mad poster strikes again.  What me worry?  Be happy!"