Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: [PATCH] [long] typeset doesn't report tied parameters (and related issues)
- X-seq: zsh-workers 43624
- From: Peter Stephenson <p.stephenson@xxxxxxxxxxx>
- To: <zsh-workers@xxxxxxx>
- Subject: Re: [PATCH] [long] typeset doesn't report tied parameters (and related issues)
- Date: Mon, 8 Oct 2018 10:05:55 +0100
- Cms-type: 201P
- Dkim-filter: OpenDKIM Filter v2.11.0 mailout1.w1.samsung.com 20181008090558euoutp01c3c0afa4b207bc63a3365ed27e132527~bltmLxGCq2801028010euoutp01I
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samsung.com; s=mail20170921; t=1538989558; bh=5qqi1SqLAM63ar38ar977FvG1tIJq/Xtgg+aRcbNPGY=; h=Subject:From:To:Date:In-Reply-To:References:From; b=Cwrt/YtCzIE59ZGuDosHpbfDM7UKl5Ue/aZWQHZuYwoRH7Ye9adUUebpX3a8Jdeuw W93e4cErvJmTG4pZhIsNKT8xu/3QnfFZLRaXY3z1xy+9cxRrbsuB0K8xw4+CggMR8F itYwhQce1KqWKc1DXSEUUmZeRk8Y3AJQInTGYHbo=
- In-reply-to: <20181007133545.zzkrbc3ed6shnk3e@chaz.gmail.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>
- List-unsubscribe: <mailto:zsh-workers-unsubscribe@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <20180924210550.carijwjibarjivu4@chaz.gmail.com> <CGME20181007133632epcas5p43a3b4c7f0fe1863478748c5cf46ce8ef@epcas5p4.samsung.com> <20181007133545.zzkrbc3ed6shnk3e@chaz.gmail.com>
On Sun, 2018-10-07 at 14:35 +0100, Stephane Chazelas wrote:
> 2018-09-24 22:05:50 +0100, Stephane Chazelas:
> It would be useful for "typeset -p", or "typeset +m" or
> ${(t)param} or $parameters[param] to report the fact that the
> array is tied (and how for typeset -p) including for special
> ones that are created as such (like PATH to path).
>
> This patch attempts to address that. While writing it, I found
> a number of related "issues" or possible areas of improvement,
> most of them minor. That ends up being quite a large change. I
> didn't initially intend to spend that much effort on it, I'm not
> very familiar with the source code (though a lot more now than
> when I started). So even though I've done quite a bit of
> testing, I think it should be reviewed by someone with more
> intimate knowledge of the code.
Thanks, I did't see anything obviously weird and it's well tested. I'm
inclined to commit it and see what happens. Any problems are most
likely to be combinations / juxtapositions that nobody's thought about.
pws
Messages sorted by:
Reverse Date,
Date,
Thread,
Author