Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: unreproducible bug with ${=...}
- X-seq: zsh-workers 45026
- From: dana <dana@xxxxxxx>
- To: frederik@xxxxxxx
- Subject: Re: unreproducible bug with ${=...}
- Date: Sat, 14 Dec 2019 09:59:49 -0600
- Cc: Zsh Workers List <zsh-workers@xxxxxxx>
- In-reply-to: <20191214045330.ehxgsufhhphg3twv@localhost>
- 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: <20191214045330.ehxgsufhhphg3twv@localhost>
On 13 Dec 2019, at 22:53, frederik@xxxxxxx wrote:
> P.S. I switched to using "zip" expansion, as suggested by Mikachu on IRC,
> which seems more elegant and doesn't use IFS: ${${:---exclude}:^^excludes}
In this case you could also just do: --exclude=$^excludes
As to why your ${=...} result sometimes differs, the most obvious thing that
comes to mind is IFS getting changed somehow. But i don't know how that would
be happening intermittently. As far as debugging, i guess just add logging to
show what IFS is set to immediately before the command, and/or run the script
with -x if you can?
dana
Messages sorted by:
Reverse Date,
Date,
Thread,
Author