Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: _dispatch (was Re: PATCH: [for consideration] TMPSUFFIX)
- X-seq: zsh-workers 39491
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: Re: _dispatch (was Re: PATCH: [for consideration] TMPSUFFIX)
- Date: Thu, 29 Sep 2016 00:30:47 -0700
- 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=y5dEfHxL4ylzosOwx2OMM3MaJ4EMo27Vo+qFzSmRPuM=; b=D1nx8LtAQc4aesNr5Vmn3re85YKUBFgAO6PTBk1j6JcXJUEiR2BjDLtL2NeSIh1+eG 7i3ieTfsMHCxHRyBjGA5uJSV2nPigjTFfmfgL4+29/EG9cWyw0BjuY4BREXrlcAUEpcG +gZ+dWd2TkchH1VL30p247qO1kiPSh0hVHm0tk36jHzqbXVQkMjjExQ4dOjjuOGFcaHk iII7QvzRidpmls0BIBRZiTXmZpSta/Qx29HOSpPU0F0qDjK8KtAXEB6YCeVaooWwzOhG d/YABM4R7keJdOCL19qz2UjeecEYlPo7QbtjFmA59qQLbm7OCN9OjdfcHa8jMInpjxVR xzEQ==
- In-reply-to: <20160929063916.GA4351@fujitsu.shahaf.local2>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <160925155112.ZM23899@torch.brasslantern.com> <20160926072546.GA28316@fujitsu.shahaf.local2> <160926091922.ZM26758@torch.brasslantern.com> <20160927070039.GA20798@fujitsu.shahaf.local2> <160927122050.ZM13394@torch.brasslantern.com> <20160928102417.GA2729@fujitsu.shahaf.local2> <160928114917.ZM32186@torch.brasslantern.com> <20160929063916.GA4351@fujitsu.shahaf.local2>
On Sep 29, 6:39am, Daniel Shahaf wrote:
}
} It might be easier to just give a flag to eval that means "propagate
} errflag of the evaluated expression to the calling scope"? So the eval
} itself would be aborted/unrolled, too.
I don't think this is a significant enough problem to warrant changing
the definition of "eval" (if by "give a flag" you mean "add a -e option"
for some variant of -e).
However, if it were possible for the "eval" builtin to know when it
was inside an "always" construct and propagate a new ERRFLAG_EVAL
out to where TRY_BLOCK_ERROR could reflect it, that might work.
The important bit would be that ERRFLAG_EVAL never converts directly
back into ERRFLAG_ERROR, so if the script ignores TRY_BLOCK_ERROR
then all errors disappear at the end of the always-block.
Or something like that.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author