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 Date: Wed, 16 Jun 1999 16:37:27 -0400 Message-Id: <199906162037.QAA30157@envy.delorie.com> From: DJ Delorie To: drh@acm.org CC: cygwin@sourceware.cygnus.com In-reply-to: <37680A14.6E904CFE@acm.org> (drh@acm.org) Subject: Re: "sed" bug? References: <19990616192340.14656.rocketmail@web119.yahoomail.com> <3767FB78.EE70381@acm.org> <199906162012.QAA29978@envy.delorie.com> <37680A14.6E904CFE@acm.org> > So is this a bug in ash? Or is the imcompatibility intentional? More likely a bug in ash (or in cygwin, but only ash stumbles upon it). We don't intentionally make them incompatible. Note, however, that bash and ash *are* different programs, so if a script relies on some obscure bash idiosyncrasy, there's not much we can do about it. -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com