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: Tue, 9 Mar 1999 19:04:17 +0100 Message-ID: <4798-Tue09Mar1999190417+0100-vzell@de.oracle.com> X-Mailer: emacs 20.3.1 (via feedmail 8 I) From: "Dr. Volker Zell" To: PRI AT cddk DOT dk CC: "cygwin AT sourceware DOT cygnus DOT com" (message from Peter Ring on 09 Mar 99 16:58:25 +0100) Subject: Re: _FANNE_Cygwin_DEV_survey References: User-Agent: SEMI/1.9.0 (Isurugi) FLIM/1.10.3 (Komada) Emacs/20.3 (i386-*-nt4.0) (with unibyte mode) MIME-Version: 1.0 (generated by SEMI 1.9.0 - "Isurugi") Content-Type: text/plain; charset=US-ASCII >> Re text/binary: NOTEPAD is not a text editor. It is a >> bug. NOTEPAD compatibility is not a valid concern. Seriously! >> Why hang on to ancient conventions such as the distinction >> between binary and text mode? >> It is useless anyway. It _used_ to be like that if a file was >> 'text', it was ASCII (aka ISO 646) text, and could be >> transmitted safely through 7-bit channels. >> That was long ago. Most of my 'text' files use 8-bit or 16-bit >> character sets, and you have to know beforehand, 'cause the >> file itself doesn't say what character set is used. I don't >> want any automatic conversion of any characters, and I most >> certainly don't want truncation at first ^Z. >> Why should I want to open a file in 'text' mode? What if I run >> a cygwin application to write a 'text' file that is part of a >> MacOS application? I need three different record separators, >> and I can't infer which to use just from what OS the >> application is running on. BTW, this is an actual example of >> what I use cygwin tools for. Finally, somebody ... :-) >> Kind regards >> Peter Ring. Volker -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com