From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3351 invoked from network); 26 Jul 2002 18:13:47 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 26 Jul 2002 18:13:47 -0000 Received: (qmail 27014 invoked by alias); 26 Jul 2002 18:13:29 -0000 Mailing-List: contact zsh-users-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 5193 Received: (qmail 27003 invoked from network); 26 Jul 2002 18:13:29 -0000 X-Authentication-Warning: sykes.suse.de: schwab set sender to schwab@suse.de using -f To: zsh-users@sunsite.dk Cc: bug-bash@gnu.org Subject: Re: POSIX compliance of shells - where to ask/talk about it? References: <20020725201713.GA17071@stu163.keble.ox.ac.uk> X-Yow: I'm in ATLANTIC CITY riding in a comfortable ROLLING CHAIR... From: Andreas Schwab Date: Fri, 26 Jul 2002 20:12:59 +0200 In-Reply-To: <20020725201713.GA17071@stu163.keble.ox.ac.uk> (igloo@earth.li's message of "Thu, 25 Jul 2002 21:17:13 +0100") Message-ID: User-Agent: Gnus/5.090006 (Oort Gnus v0.06) Emacs/21.3.50 (ia64-suse-linux) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit igloo@earth.li (Ian Lynagh) writes: |> Hi all, |> |> Where should one ask/talk about POSIX shell compliance (looking for a |> mailing list probably)? |> |> I am reading the standard at |> http://www.opengroup.org/onlinepubs/007904975/utilities/xcu_chap02.html |> and finding it very imprecise - disappointingly so (am I looking in the |> wrong place?). I am therefore looking to implementations to clarify the |> standard, but with things like this (all shells invoked as sh, bash |> given --posix): |> |> printf "%s\n" `echo '\\\\\\\\\\\\\\\\'` |> printf "%s\n" "`echo '\\\\\\\\\\\\\\\\'`" |> |> Using shells/ash: |> \\\\ |> \\\\ |> |> Using shells/bash: |> \\\\\\\\ |> \\\\\\\\ |> |> Using shells/zsh: |> \\\\ |> \\\\\\\\ I think the key difference here is whether echo is interpreting backslashes or not. By default, bash's builtin echo does not interpret backslashes, and if you use "echo -e" you get the same output as ash. zsh seems to be the odd case again. Andreas. -- Andreas Schwab, SuSE Labs, schwab@suse.de SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."