Delivered-To: listarch-cygwin@sourceware.cygnus.com Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com Date: Wed, 17 Feb 1999 13:07:08 -0500 Message-Id: <199902171807.NAA16764@envy.delorie.com> From: DJ Delorie To: paul-ml@is.lg.ua CC: corinna.vinschen@cityweb.de, cygwin@sourceware.cygnus.com In-reply-to: <17817.990217@is.lg.ua> (message from Paul Sokolovsky on Wed, 17 Feb 1999 19:37:11 +0200) Subject: Re: Cygwin B20 - fseek under gcc fails to reposition on text files References: <36CA92B5.844635AA@cityweb.de> <17817.990217@is.lg.ua> > And finally, from where all this stuff might be originated - it may > be done whatever wanted, but if, when writing to console we get clobbered > output without carrage returns, it doesn't cost a cent. That's where > myth of win32 speciality breaks down - Win32 console, as any other > console in cooked mode (Linux, say) performs implicit cr after lf, > when there's no explicit. To add fact to the myth, if you bring up such a file (\n without \r) in notepad, it does not do the right thing - it very explicitly looks for the CR/LF pair to mean a line ending, and no other ending will do. Batch files also cannot have NL endings - they need CR/LF endings. Of course, this really just means that the programmers were short-sighted, but it's still a fact we must live with. -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com