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=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FROM,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham 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 c97c7163 for ; Thu, 11 Jul 2019 01:41:12 +0000 (UTC) Received: (qmail 2607 invoked by alias); 11 Jul 2019 00:47:43 -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: 24045 Received: (qmail 3558 invoked by uid 1010); 11 Jul 2019 00:47:43 -0000 X-Qmail-Scanner-Diagnostics: from mail-vs1-f68.google.com 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(209.85.217.68):SA:0(-0.7/5.0):. Processed in 2.539213 secs); 11 Jul 2019 00:47:43 -0000 X-Envelope-From: sgniazdowski@gmail.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.217.68 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=N5PjKmZki5n+GTlTlO6u67EWigt29K3ebOcixOeZW+k=; b=CByrzFASIr92t4cRkU/oAO1TGVnRWGqBej3/pirSgzL3paUgtZi0SdTqB6hw0Y+SC/ 88mwejaO6bVZqRdoZawGFf5aj5jvBsz1p9GS80cTl6WomoNu/RdQGHnrOOetSGw59fRq 17gKINMAvoW9jpqCvIUKCNWuYuM6cBBLyY7SrGMBc1Zb++gU3zlmEHHsxdEnIe3A9L3Q Tn87dEeFdfe1zS72BojZuOxUGDUbMovN9gwHlAFAHOu61y0XKurRmQ7gn9lIUyCji4sB llETEkqTK8aMVM277NpgHtVY/WxJ9Dsv75q3QqArZQn9DaIM3BRp7hDuEi5vY+Lzggvg +Eyg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=N5PjKmZki5n+GTlTlO6u67EWigt29K3ebOcixOeZW+k=; b=pRQBUK9Y4Vk+VqKkmJX28o3eY8tu/Yp82qZrImfSuTf62PZl6nsyQ+U0TDM8l5UhR8 +hwns8qnZhgCdq/wCmtulBfJdkIW9675fRUWAXQrye2xGmprEQJC2Sv1RZgI7nDhUwnD vSp9Lvun+JUDV26YLVA+qAy35gQIMKIsneFq+4YkBPm78UXsoEvf73Uy+EK0Z64oXs8R 5Zs9opbg811pHOWIqxXF4l0R2piac2lRNFEnVVj6hpzuSENFXxX6Zbnt4FLs4CIwO+8x 5G8kZI+/hCv8wEpKcOKPQz/RakG/D58yRFLlo9y9IWT1Z3Us8YuyBwvng+/8wS7bNy0q an5Q== X-Gm-Message-State: APjAAAVH2Fwa2Xf08sCbyFYOi2qJkxLpb2d477n0uStXqhI2mfWfKRK4 XFU2WF9JgttICyEOP7a68bV7jYLqOlnOZmO99mejcu/6AcE= X-Google-Smtp-Source: APXvYqytSIQOh9QlNbaDwenUbyxwnLZDxABNYcEAHvKqv48kCzJmKLroqt7UaaQuOdOPQWbzUBIb849iM3r9cB+IYQ4= X-Received: by 2002:a67:ead3:: with SMTP id s19mr609619vso.147.1562806027947; Wed, 10 Jul 2019 17:47:07 -0700 (PDT) MIME-Version: 1.0 References: <20190710224713.GA30662@spodhuis.org> In-Reply-To: <20190710224713.GA30662@spodhuis.org> From: Sebastian Gniazdowski Date: Thu, 11 Jul 2019 02:46:56 +0200 Message-ID: Subject: Re: Is there some bash source that Zsh will not parse? To: Phil Pennock Cc: Zsh Users Content-Type: text/plain; charset="UTF-8" On Thu, 11 Jul 2019 at 00:47, Phil Pennock wrote: > > 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: > > ... > 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. Yes but i meant actually just the parser. I believe the contents of ${...} are taken as a whole by the parser to then be passed to stringsubst() and the like, so that would be a "late"-parsing, which i'm not interested in currently. > 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. Yeah, that would be interesting :) > -Phil -- Sebastian Gniazdowski News: https://twitter.com/ZdharmaI IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin Blog: http://zdharma.org