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 X-Injected-Via-Gmane: http://gmane.org/ To: cygwin AT cygwin DOT com From: Andrew DeFaria Subject: Re: ash does not understand '~' Date: Fri, 17 Oct 2003 08:35:40 -0700 Lines: 18 Message-ID: References: <20031017102823 DOT GP25076 AT cygbert DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet AT sea DOT gmane DOT org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en,ru In-Reply-To: <20031017102823.GP25076@cygbert.vinschen.de> Corinna Vinschen wrote: > On Fri, Oct 17, 2003 at 12:19:36PM +0200, Ralf Habacker wrote: > >> Hi, >> >> the following shell script does not work at least with ash-20031007-1 >> although I don't see any reason why this should not be a valid >> syntax. If you use > > The reason is, '~' is an extension to the bourne shell syntax, first > defined in csh or tcsh, AFAIK. ash is a pure bourne shell with next to > no extensions. Using '~' in a shell script is non-portable. Non-protable to such "OSes" that don't have a more modern shell then Bourne/Ash I guess. Are there any "OSes" that don't support shells like csh, tcsh, ksh, bash? -- 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/