delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/1998/01/07/18:26:52

From: sab AT seanet DOT com (Scott Blachowicz)
Subject: Re: Why text=binary mounts (Re: Gnu-win32 (b18), coolview and NTEmacs)
7 Jan 1998 18:26:52 -0800 :
Message-ID: <uen2kytpf.fsf.cygnus.gnu-win32@seanet.com>
References: <19980107132827 DOT 10951 DOT qmail AT hotmail DOT com>
Reply-To: sab AT seanet DOT com
To: "Earnie Boyd" <earnie_boyd AT hotmail DOT com>
Cc: gnu-win32 AT cygnus DOT com

"Earnie Boyd" <earnie_boyd AT hotmail DOT com> writes:

> Let me remind you that the purpose of the cygnus gnu-win32 project is to 
> port UNIX code.  Most of the UNIX world programs choke on the \r\n 
> combination.  Therefore text=binary is the easiest solution.

Yes, I realize that.  But it seems like there are some concessions being
made to the folks who claim that the tools ought to interoperate more
easily with the DOS tools (e.g. accepting file paths like "c:/windows").
So, I keep hoping that someone will come up with some clever scheme to do
away with this text=binary mount stuff (which seems to be one of the most
awkward things about trying to use the gnu-win32 stuff).

I keep hoping to be able to find some affordable (read: negligible
monitary cost :-)) alternative to MKS sh (or whatever) to give me a Unix
toolset that can interoperate with the Windows developers and development
tools that I need to.
-- 
Scott Blachowicz                <sab AT seanet DOT com>

-
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 -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019