Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com Message-ID: <37680A14.6E904CFE@acm.org> Date: Wed, 16 Jun 1999 16:33:24 -0400 From: "D. Richard Hipp" Organization: Hwaci X-Mailer: Mozilla 3.0Gold (X11; U; Linux 2.0.36 i686) MIME-Version: 1.0 To: DJ Delorie CC: cygwin@sourceware.cygnus.com Subject: Re: "sed" bug? References: <19990616192340.14656.rocketmail@web119.yahoomail.com> <3767FB78.EE70381@acm.org> <199906162012.QAA29978@envy.delorie.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit DJ Delorie wrote: > > > I don't understand. "sh" is "bash" on both Linux and Cygwin20, is > > it not? I'm not running csh if that is what you are asking. > > sh and bash are different in cygwin. sh is really "ash", which is > like bash but doesn't have all the interactive bits in it, making it a > much smaller and leaner shell, good for scripts. OK. That's good to know. When I type: bash //H/gd/acd/fu/re/configure instead of just //H/gd/acd/fu/re/configure everything appears to work. So is this a bug in ash? Or is the imcompatibility intentional? Thanks everybody for your help. -- D. Richard Hipp -- drh@acm.org -- http://www.hwaci.com/drh/ -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com