From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.3 required=5.0 tests=DKIM_ADSP_ALL,DKIM_INVALID, DKIM_SIGNED,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=no autolearn_force=no version=3.4.2 Received: from primenet.com.au (ns1.primenet.com.au [203.24.36.2]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id f49d9d6a for ; Wed, 10 Jul 2019 22:48:09 +0000 (UTC) Received: (qmail 24326 invoked by alias); 10 Jul 2019 22:47:57 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: List-Unsubscribe: X-Seq: 24044 Received: (qmail 6989 invoked by uid 1010); 10 Jul 2019 22:47:57 -0000 X-Qmail-Scanner-Diagnostics: from mx.spodhuis.org by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.101.2/25503. spamassassin: 3.4.2. Clear:RC:0(94.142.241.89):SA:0(-4.3/5.0):. Processed in 1.653323 secs); 10 Jul 2019 22:47:57 -0000 X-Envelope-From: zsh-workers+phil.pennock@spodhuis.org X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at spodhuis.org designates 94.142.241.89 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=spodhuis.org; s=d201905; h=In-Reply-To:Content-Type:MIME-Version:References :Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding :Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=DSfnhsqA7Nn3SWvnGp5E3aqowMw1IJNIpHIQBldXdnc=; b=FmfRBXJCwQePwMKF+mMJwo504L HXq1pg++jYg9sacxx11uYR1783coT1TSHmdJz+7yYiJX6/dviWnqUhdybrhGeEmKCSzzH/E8n6IfL iFnOaOETXAYyHQumItgcjmttTlc11NVa08EZ9Clj3BWshshm2EDXC0OlConM5qgQ5bSVhAppNKKxU RCqQQbkT4mEXA9abY0DpOw0buxZJZZ4l4BuJZSXdMBp+HDucYsywMRg4Zo7tOvG1i568fz6mNZAJg wLfMscIEdMrNRaSiYcTBn20bZ4u0WGxY5w3e+dD57e96L08zexn3j3JpPyZX+UgejJWQNvCOvMaLo aDMVSeIw==; DKIM-Signature: v=1; a=ed25519-sha256; q=dns/txt; c=relaxed/relaxed; d=spodhuis.org; s=d201905e2; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=DSfnhsqA7Nn3SWvnGp5E3aqowMw1IJNIpHIQBldXdnc=; b=fRWz2r53nFAru8E0DwjjnnXPi w2alSiUdgkcUriUns/UypLTn5qwoGYoBG3V2/oXYsgnZIWrharOqvp53elCCA==; Date: Wed, 10 Jul 2019 18:47:14 -0400 From: Phil Pennock To: Sebastian Gniazdowski Cc: Zsh Users Subject: Re: Is there some bash source that Zsh will not parse? Message-ID: <20190710224713.GA30662@spodhuis.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: OpenPGP: url=https://www.security.spodhuis.org/PGP/keys/0x4D1E900E14C1CC04.asc On 2019-07-10 at 18:10 +0200, Sebastian Gniazdowski wrote: > in the opposite direction, this is rather true, e.g. the globbing > flags aren't parsed correctly: Plenty, since Zsh has never until now aimed to be a complete superset of Bash functionality; instead, we've added features to make it easier to interoperate, eg making sure that command remote command-lines would work. Note in particular that where zsh has ${(flags)varname} for parameter expansion flags, bash has ${varname@operator} syntax for expansion transformations. There's other stuff around indirect variables, case modification expansions, and `shopt`, which all come to mind. Almost certainly a lot more. If Zsh's goals are changing such that complete Bash compatibility is required in bash mode (as opposed to "enough to get by") then it might be worth trying to run the bash test suite against Zsh, with suitable modifications to ensure Zsh is in the correct mode always. That should prove ... educational. -Phil