delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm |
Sender: | cygwin-owner AT sourceware DOT cygnus DOT com |
Delivered-To: | mailing list cygwin AT sourceware DOT cygnus DOT com |
Date: | Wed, 16 Jun 1999 16:37:27 -0400 |
Message-Id: | <199906162037.QAA30157@envy.delorie.com> |
From: | DJ Delorie <dj AT delorie DOT com> |
To: | drh AT acm DOT org |
CC: | cygwin AT sourceware DOT cygnus DOT com |
In-reply-to: | <37680A14.6E904CFE@acm.org> (drh@acm.org) |
Subject: | Re: "sed" bug? |
References: | <19990616192340 DOT 14656 DOT rocketmail AT web119 DOT yahoomail DOT com> <3767FB78 DOT EE70381 AT acm DOT org> <199906162012 DOT QAA29978 AT envy DOT delorie DOT com> <37680A14 DOT 6E904CFE AT acm DOT 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 AT sourceware DOT cygnus DOT com
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |