Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: NOMATCH errors
- X-seq: zsh-users 22338
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-users@xxxxxxx
- Subject: Re: NOMATCH errors
- Date: Sun, 8 Jan 2017 10:35:49 -0800
- 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==
- In-reply-to: <1483673721.1546772.838942313.0683A864@webmail.messagingengine.com>
- List-help: <mailto:zsh-users-help@zsh.org>
- List-id: Zsh Users List <zsh-users.zsh.org>
- List-post: <mailto:zsh-users@zsh.org>
- Mailing-list: contact zsh-users-help@xxxxxxx; run by ezmlm
- References: <1483673721.1546772.838942313.0683A864@webmail.messagingengine.com>
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.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author