From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2403 invoked by alias); 30 May 2015 22:28:39 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 35342 Received: (qmail 1586 invoked from network); 30 May 2015 22:28:37 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.0 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version:content-type; bh=nP1ncqdosI+nW2X37Wd+wYFe6mAD0maxeuuj4cCUtKc=; b=SCkKybP0OQuS3woBT3z030hcqZfdrmPv0GQ2r+rdCE80S9tjsyjJfzibFueOTiMviR HJeFRGI6lnGRqR8thfgR0Y86yTbjFqQ2fG2KjRTSdEO5882z1Xgcin4w59ntksIXCcvZ CwxWqn4F95RFyGYEKH6ddYCDQh0nIwo9Yi6+cF2nxVu63snZs8vlKoTdvxRz1hNTta8x lufJWEXVlo7zOXYp4fZheHLZQUEwzRAig6QXrzbm8WetIQqKt2g61uhcanjfofxv15BQ 8unE0wMaDmToVNNI2jNAXverQIXe2DBeoPXKqzCzJ6CjR5q36qh64S0JTTBRr8Z8xMAs VAjQ== X-Gm-Message-State: ALoCoQkxiKshgxHw3fvfdJzn0Mj74fQHH7YpRjufWTp/ZKsmusDtAqINrLxLEbGP+zifiboKQELh X-Received: by 10.60.45.201 with SMTP id p9mr4328583oem.82.1433024915172; Sat, 30 May 2015 15:28:35 -0700 (PDT) From: Bart Schaefer Message-Id: <150530152831.ZM17344@torch.brasslantern.com> Date: Sat, 30 May 2015 15:28:31 -0700 In-Reply-To: <20150530204046.0ae57c98@ntlworld.com> Comments: In reply to Peter Stephenson "Re: Arith parsing bug with minus after $#" (May 30, 8:40pm) References: <55676FB1.9080401@inlv.org> <20150529160237.6f329071@pwslap01u.europe.root.pri> <5568BF27.80806@inlv.org> <5423831432932500@web1o.yandex.ru> <20150530202412.2ff6de78@ntlworld.com> <20150530204046.0ae57c98@ntlworld.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: Zsh hackers list Subject: Re: Arith parsing bug with minus after $# MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On May 30, 8:40pm, Peter Stephenson wrote: } } What I'm not sure about is how to decide. SH_WORD_SPLIT isn't the } same thing, though there's an obvious mnemonic for why it might have } this effect. We have the option of basing it on emulation alone, but } that always strikes me as something of a counsel of despair. POSIX_IDENTIFIERS, perhaps?