delorie.com/archives/browse.cgi | search |
From: | epeschko AT elmer DOT tci DOT com (Ed Peschko) |
Subject: | Re: bash 2.01/cygwin.dll problems |
7 Sep 1997 21:31:39 -0700 : | |
Approved: | cygnus DOT gnu-win32 AT cygnus DOT com |
Distribution: | cygnus |
Message-ID: | <199709070449.WAA04788.cygnus.gnu-win32@or3-sun106.tci.com> |
Original-To: | sos AT prospect DOT com DOT ru (Sergey Okhapkin) |
Original-Cc: | gnu-win32 AT cygnus DOT com |
In-Reply-To: | <01BCB9F1.5E965A60@gater.krystalbank.msk.ru> from "Sergey Okhapkin" at Sep 5, 97 11:46:35 am |
X-Mailer: | ELM [version 2.4 PL23] |
Original-Sender: | owner-gnu-win32 AT cygnus DOT com |
> > Tibor Polgar wrote: > > starting less or vim. It also doesn't want to accept my .bashrc (works > > fine with the b18 bash). > > > > startup message is: > > > > bash.exe: d:/tibor/.bashrc: error 0 > > FAQ :-) Remove <CR>'s from .bashrc. hey -- If it's a FAQ, shouldn't the text for the error be something like: Error 0: Remove <CR>'s from .bashrc. or somesuch? Ed (PS: I do agree - unix binaries should be produced by default, not win32 ones.) (PPS: if win32 binaries are produced, will fork() et al. be able to be run?) - 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".
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |