Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 17 Oct 2003 11:30:37 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: ash does not understand '~' Message-ID: <20031017153037.GA10560@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Fri, Oct 17, 2003 at 02:36:54PM +0200, J?rg Schaible wrote: >Corinna Vinschen wrote on Friday, October 17, 2003 1:04 PM: >> On Fri, Oct 17, 2003 at 12:37:10PM +0200, J?rg Schaible wrote: >>> BTW: It does also not know the "[ ]" syntax for a built-in test, you >>> always have to use "test": >>> >>> if test -f /etc/hosts; then >>> echo "/etc/hosts exist!" >>> fi >> >> Beep. Wrong. It knows [ ] >> >> Corinna >> >>> and you cannot combine export with an assignment, you have to write >>> separate statements: >>> >>> VARIABLE=test >>> export VARIABLE >> >> Beep. Wrong, too. export var=value is a vaild bourne shell syntax. > >Did that change at some point? I remember having really big problems >writing scripts running on a on Solaris, Linux and Cygwin some years >ago and IIRC it was basically because of ash at that time ... It must have changed because I recally ash not accepting that syntax, too and I know that older versions of /bin/sh don't like it. ash does understand it now, though. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/