Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: _dispatch (was Re: PATCH: [for consideration] TMPSUFFIX)
- X-seq: zsh-workers 39488
- From: Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: Re: _dispatch (was Re: PATCH: [for consideration] TMPSUFFIX)
- Date: Thu, 29 Sep 2016 06:39:16 +0000
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= daniel.shahaf.name; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=ydbcYB71pdSdrGAU Ku6y2/PQ6SY=; b=xEGWy2D0RQTZofNeB1IFGVS3krD3RM2zn5xaxUokEYfJ2aRf 9eptGNmdWGMllPxdVZBtI8gYiYRC+RYJ/NJOwrACp4bhCk8p1qpc1XXt+ASFYMhj CwcMDRwRzPwencpJJa8jL4L2t0jeOr2lpdI3+gy3sU0/bQhs4JJiZN6mhlQ=
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=ydbcYB71pdSdrGA UKu6y2/PQ6SY=; b=Bp55MV1d8K8iJOtLPqmS2t/vE/u4zbuUnvH+r+zI533a6T6 zZigP9pp518X22LoU/ZjD2ChRb4o5ZlmG2FcroogNtChfE4hj5MFZBw9UMXImGJu f7DBsNHmQmHzVhTcCdpw0Z9G6+H/lWRS4bpr8Nmv5z89t/gN5y6iYc40yVcw=
- In-reply-to: <160928114917.ZM32186@torch.brasslantern.com>
- 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>
Bart Schaefer wrote on Wed, Sep 28, 2016 at 11:49:17 -0700:
> } + {
> } + eval "$comp" && ret=0
> } + } always {
> } + if (( TRY_BLOCK_ERROR )); then
> } + ... throw the exception ...
> } + fi
> } + }
>
> Sadly, that won't do it either -- TRY_BLOCK_ERROR is not set:
>
> The eval captures everything and turns it into nonzero exit status.
>
⋮
> compdef 'compadd *' f
>
> There might be another way to permit that without eval'ing, but it
> would be convoluted.
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.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author