From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12809 invoked by alias); 8 Jan 2017 19:02:34 -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: X-Seq: 22338 Received: (qmail 2052 invoked from network); 8 Jan 2017 19:02:34 -0000 X-Qmail-Scanner-Diagnostics: from mail-ua0-f170.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.217.170):SA:0(-0.0/5.0):. Processed in 1.436458 secs); 08 Jan 2017 19:02:34 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_PASS,T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: schaefer@brasslantern.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.170 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:date:in-reply-to:comments:references:to:subject :mime-version; bh=sOKndwmJI3sGhVJ+FRLKt3bhSxsXE4HPgm0JaB3joLU=; b=oGWfnT0YUB3VjXuiGXvd7Ubd4AhQYML0ZIAhnr0PvkKUpiJffJPxExuqYHCxnttKcC 7qmsPFgzAgjBmZOVlHGk/c0l643pPSiG+x3S9gKpTixcrXGSnaUn6u/4542/bcyhGUOY ACiiFVcBC7jF6xZp9wALpfv2TF3BWijE+KMxIdDD/eLry/+vlzeRp146xPVvHthBiQbE zZdXUYV1ngJOO8prjg8g8miirtxZxdRc8gp82+3d2j52rKELifuR5rbBtIDBW151yfKE C/gmwtWgPgcY2YEMt2JBbeyWOLWRweG3zFLwgISwJaMOZGQdLvVRMbIOlmDwdoRR+eVG eHIg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version; bh=sOKndwmJI3sGhVJ+FRLKt3bhSxsXE4HPgm0JaB3joLU=; b=bPAC1viYObHOB+n3AyFOVFRyQWORdR5PPUTagKcdADPGJDTxWbLT3/ryM6Pb6roFmT D6Ek1IOecqEP5MomnfbKJg+Y/i084wetbb1BZvlPsxwIJ0mCPoakl9MPjaQbX538uywd mrG7ywJ4LYliiHwCFFqNMBg/+uOrmz7VuUj28JkDCs6uW1kHDj/V9iO69kEboEs+Y3gD 0YIlXJw6E9t5eLOY2UqXOgH3qhXfCPF2BiAmCMFg5g6lLkI+KdXVxNDCXUt7YjCXOw12 5njHVEP2WHsSPbR7WDwjnm/Zmwj7+Uvl/fpl3R2tv1KZtd/t3QtY+s9HR21t8UTuT7JO rBrg== X-Gm-Message-State: AIkVDXJVUs/ZY+J+qqDNydNcndPYrmFPykndHpFSZkCQTm4dQveAY2gNcjLRoZUs/4QVPg== X-Received: by 10.159.41.163 with SMTP id s32mr68034564uas.137.1483900544321; Sun, 08 Jan 2017 10:35:44 -0800 (PST) From: Bart Schaefer Message-Id: <170108103549.ZM8736@torch.brasslantern.com> Date: Sun, 8 Jan 2017 10:35:49 -0800 In-Reply-To: <1483673721.1546772.838942313.0683A864@webmail.messagingengine.com> Comments: In reply to Anthony Heading "NOMATCH errors" (Jan 5, 10:35pm) References: <1483673721.1546772.838942313.0683A864@webmail.messagingengine.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-users@zsh.org Subject: Re: NOMATCH errors MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Jan 5, 10:35pm, Anthony Heading wrote: } } echo hello } echo =hello =hello } echo "is there anybody in there?" } } doesn't get past: } hello } hello:2: hello not found } } Interestingly the docs perhaps arguably seem to imply differently: } Fatal errors found in non-interactive shells include: } [...] } o File generation failures where not caused by NO_MATCH or similar } options This particular bit of doc is out of date. Which is to say, either the doc should have been changed or a bug was introduced. This appears to date from workers/30789 which introduced the option CONTINUE_ON_ERROR. This changed default startup-script behavior from blowing right past all sorts of syntax problems, to aborting on those errors. Setting the option restores the old behavior. Unfortunately NO_MATCH errors got swept into the bucket along with all the other startup-time errors, so there's now no way other than using an "eval" wrapper or an "always" block to safely skip NO_MATCH errors without also skipping more serious errors like broken loop control syntax. So ... either we need to undo that side-effect of CONTINUE_ON_ERROR or we need to update the documentation quoted above.