Path: utzoo!utgpu!watmath!watdragon!crocus!rtczegledi From: rtczegledi@crocus.waterloo.edu (Richard Czegledi) Newsgroups: comp.sys.amiga.tech Subject: Re: DME and vanishing text Summary: plea for no lf's at the end of line. use cr/lfs please? Message-ID: <15874@watdragon.waterloo.edu> Date: 12 Aug 89 02:20:36 GMT References: <89222.135727WTW101@PSUVM> Sender: daemon@watdragon.waterloo.edu Reply-To: rtczegledi@crocus.waterloo.edu (Richard Czegledi) Distribution: comp.sys.amiga.tech Organization: U. of Waterloo, Ontario Lines: 24 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). ------------------------------------------------- We were developing a new line eater organism, but it escaped from the culture dish, ran rampant through the lab and crawled into a machine where it multiplied. Then it ate all of the signature files. But we managed to contain it before it went through the net{{{{^ 'YUM'