From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: zsh-workers-return-43604-ml=inbox.vuxu.org@zsh.org X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,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 8fb48068 for ; Thu, 4 Oct 2018 20:35:26 +0000 (UTC) Received: (qmail 2076 invoked by alias); 4 Oct 2018 20:35:15 -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: List-Unsubscribe: X-Seq: 43604 Received: (qmail 24399 invoked by uid 1010); 4 Oct 2018 20:35:15 -0000 X-Qmail-Scanner-Diagnostics: from mail-lf1-f45.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(209.85.167.45):SA:0(-1.9/5.0):. Processed in 3.690922 secs); 04 Oct 2018 20:35:15 -0000 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=TJan9fhpiu0En0XHRxCS2vZ7DEWxlFGtc5JUwwH0eGU=; b=S+F6TZuKAic1regmyI5UIqcxJrhHn6ORv8BlXkaeDUZsOafQyoziHfMX7+XqhhIIvd oHys3HtLY/mgTOspeRASOH4Ffgb9F1mzvXwlzC4xcQPXL9/oskFic2JgkyyMkecBftrK R+wPv+6i83M24+ohr0VURRnS6/NhtS5yLSwip7PiYCxUzpdo2dSgPxnKcohQPfImI485 XIDKAxZnPlm4rdl7eV98/Q1d0d8zAkHjgGZefg4mNWZUQecU+mIbOrMqdL9wqNeDef2c WNe3tDoxOqDHVLJyWDYDeq2NhzC1lix/eohtfJrRwBFnUxbrK2Y2debk6D5aSpj2Oklz l1Zg== 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=TJan9fhpiu0En0XHRxCS2vZ7DEWxlFGtc5JUwwH0eGU=; b=fxNvyHg/dBTe14q0HgA0zV/q01qsa8ab08bzzfCBVzZcyYkWSEJGfddym/kjhSyjYm xBgH+zFoQNPkmx0h3wzmdZXtX9wrv24pjKC5cbCQHE9tPHFB1Spn8ACgwBn2e/9qviF8 pR6WPD0Wc5ELekesuZ/7J3S9/ADX95uztL4Hwq5fJ9dEmd8axcGPFZMPkZclweMiAnUB cINyLf0eGmcUcNMT5HecIS3oOJE4k9SPsBTcsRSFqIuB41S/mPBIlVjpOmAgFRvET12Z 88ArxxRFDk8YymvEcXepuPXBQWqP5io2tYyt0qZTE0fvJgyiOzWFgSCnhRBxriC8ygwM ZBDg== X-Gm-Message-State: ABuFfojLI7ZU+ejajJBGY+oII0RzkRc4QUODZVPK9osPt3shybqw2OHn re3kzZyd39l8iu5ObUN1Sc2Q/2mWUS7cmDFDDzP5iA== X-Google-Smtp-Source: ACcGV63XYuEsP2boNW6F1zOaL95NRbmgRN5ZNDIe+uxa9N541HZ+oFL1QtSIY0tWS/CKAl2FIGghzOyvfewoc2e5a+k= X-Received: by 2002:a19:434f:: with SMTP id m15-v6mr4817148lfj.142.1538685307245; Thu, 04 Oct 2018 13:35:07 -0700 (PDT) MIME-Version: 1.0 References: <20181004163158eucas1p234a045be013b5463d8db44314ed217dc~adN28lJmq0822408224eucas1p2F@eucas1p2.samsung.com> In-Reply-To: <20181004163158eucas1p234a045be013b5463d8db44314ed217dc~adN28lJmq0822408224eucas1p2F@eucas1p2.samsung.com> From: Bart Schaefer Date: Thu, 4 Oct 2018 13:34:53 -0700 Message-ID: Subject: Re: Parse error (lack thereof) on incomplete loops To: Peter Stephenson Cc: "zsh-workers@zsh.org" Content-Type: text/plain; charset="UTF-8" On Thu, Oct 4, 2018 at 9:32 AM Peter Stephenson wrote: > > On Thu, 2018-10-04 at 08:49 -0700, Bart Schaefer wrote: > > > % { while false > > cursh while> } > > % > > > > This indicates a parsing problem in 5.6 > > It affects for, repeat, until and if, too, and isn't hard to turn back > into a parse error. How did it stop being a parse error in the first place? > However, I'm very far from convinced this is actually a bug. If you > turn off SHORT_LOOPS you'll find you get the error back My problem with it is that it's not consistent. set -x { while false while false } The shell is now in an infinite loop executing "false". Can this really be intentional?