From:	jazz AT opennt DOT com (Jason Zions)
Subject:	Re: More on getting coolview-bash to work with emacs
9 Dec 1997 13:44:14 -0800 :
Message-ID:	<348DB4BE.69EC48C8.cygnus.gnu-win32@opennt.com>
References:	<01BD04C9 DOT 889A67C0 AT gater DOT krystalbank DOT msk DOT ru>
Mime-Version:	1.0
To:	Sergey Okhapkin <sos AT prospect DOT com DOT ru>
Cc:	"'Arlindo da Silva'" <arlindo AT niteroi DOT gsfc DOT nasa DOT gov>,
	"gnu-win32 AT cygnus DOT com" <gnu-win32 AT cygnus DOT com>

> I do not understand the needs of text mode at all. Neither NT posix
> subsystem, nor OpenNT, nor UWIN doesn't have text mode as default.

If I understand the arguments, Sergey, the basic difference is that the
goals of the NT Posix subsystem, OpenNT, and UWIN are different from the
goals of cygwin.

The first three are aimed are providing (forgive the simplification and
trademark abuse) UNIX on top of NT. Users live in a Unix world, where
there is only one line-ending and \n is its name.

Cygwin has multiple goals; while "Unix on NT" is one of them, it appears
to be of less importance than the others: a free development environment
for Win32, a way of getting more tools more rapidly into the Win32
world, etc. In meeting those goals, supporting the Win32 line-ending of
\r\n is relatively important. Folks living in the Win32 world don't want
to give up Win32 tools that operate on text files; because of that, they
need cygwin to deal properly with \r\n-style text files.

I'd like to contribute to a solution for living in a mixed line-ending
world, but I haven't found a coherent way of solving the problem short
of living in one world or the other and abandoning attempts to handle
both line-endings simultaneously. That's not a helpful position for
those who have a goal other than "Unix on NT", so I say nothing.

Jason Zions
Softway Systems Inc.
Makers of OpenNT, POSIX and more for Windows NT
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -