Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Date: Thu, 18 Feb 1999 18:38:46 +0200
From: Paul Sokolovsky <paul-ml AT is DOT lg DOT ua>
X-Mailer: The Bat! (v1.00 Christmas Preview) UNREG
Reply-To: Paul Sokolovsky <paul-ml AT is DOT lg DOT ua>
Message-ID: <17776.990218@is.lg.ua>
To: Corinna Vinschen <corinna DOT vinschen AT cityweb DOT de>,
        DJ Delorie <dj AT delorie DOT com>, cygwin AT sourceware DOT cygnus DOT com
CC: Steve Morris <smorris AT nexen DOT com>
Subject: Re[2]: Cygwin B20 - fseek under gcc fails to reposition on text files
References: <36CB35C9 DOT 86D45693 AT cityweb DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hello Corinna,

Corinna Vinschen <corinna DOT vinschen AT cityweb DOT de> wrote:

>>     So, for more than twenty years MS maintains myth about "special
>> format" of text files of their systems. It's hardly believable. Since

CV> The best way would be to throw away and ignore any newline with
CV> more than one single character.

    Yes, and bad thing is that people came say, from Unix, and don't knowing
that here text files are special, but constantly getting binary file
corruptions when filtering gifs, piping gzips, etc. may think that way is
right ;-(

CV> But let's get serious.

CV> IMHO, above all text file processing should be done according to the
CV> underlying OS and it's vendor, also if this is wretched.

    Bad thing is that issue very minor. People might don't care what
line-endings text files have, they might don't care that there's
notepad and bat files. And when their favorite vi chokes on that \r at
the end (or beginning? ;-) ) of line they might teach him chop it -
after all, that's not notepad. But they might think that wrapping each
command piping binary files in shell script setting CYGWIN (having
spent some nice time trying to understand why their files are
corrupted and asking maillist why this bug) is too awkward.

   Of course, that far too imaganable picture, just like my previous
massage has, just like several years ago cygwin itself was only
imaganable. I don't believe that things enpictured by me will be, or
even should be, done to cygwin. I just wanted to hyperbolize it,
showing that changing itself is not an edge alternative, all
determained by ammount of changes, and there might be the golden mean,
exactly what you'll do. (That's just because I have a ho that Cygnus
guys quite conservative - I remember Christopher Faylor's hesitating
in cygwin-developer whether correcting bug won't break user (or
customer) code. Maybe you, Corinna, as leading contributor, and DJ, as
author of alternative approach, and working for Cygnus, have other
opinions).

   But there still that idea - there maybe niche that cygwin doesn't
fill - to be more unixish despite be less winnish.

CV> The second choice has the advantage, to be easy to implement.

CV> The third choice should be implemented, if s.o. has nothing important
CV> to do.

CV> Regards,
CV> Corinna

    Thanks for not taking previous text as profanity, that's was just rebellion
humoresqe, just forgot adding trailing disclaimer ;-)


Best regards,
 Paul                            mailto:paul-ml AT is DOT lg DOT ua


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com