From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from primenet.com.au (ns1.primenet.com.au [203.24.36.2]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id 2c0ddd8f for ; Sat, 14 Dec 2019 16:00:36 +0000 (UTC) Received: (qmail 6288 invoked by alias); 14 Dec 2019 16:00:29 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: List-Unsubscribe: X-Seq: 45026 Received: (qmail 7734 invoked by uid 1010); 14 Dec 2019 16:00:29 -0000 X-Qmail-Scanner-Diagnostics: from mail-yb1-f170.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.1/25656. spamassassin: 3.4.2. Clear:RC:0(209.85.219.170):SA:0(-1.9/5.0):. Processed in 4.432033 secs); 14 Dec 2019 16:00:29 -0000 X-Envelope-From: dana@dana.is X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.219.170 as permitted sender) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=tm2qatYK0ZZsOCqi0yg2/R7DtSF9UKZyssmGRq8ivbo=; b=EIX6b9xEPGXfCc6c1hJrOUoM/+fuJW3MkPKxx+9r4XdTWpdqaeqRFDzAxrnOtQP3gs N5fYZyErJjjVZvrdPWevd4LhbDu12VplEJWgWgQ0af+cpUZGFt2J4fNbU1QabcqDxVq5 bcbVPJTH2aRIfGW+nfVrHqAPhql+L+kY9o59xDIyMdfiDN6wOpzHAy+7ecC7uOqxi3EH RNngYRi7IaMLFEfW7sGLWTJgdo9fV6vLx+YZWJ1JldiBjVOp6vp5BYc1KPRyO0r8tA9t 7U0AI35AW630kut00xDO9PlS2x364+5vKOimc/JjjRmT7lovf807AQ5nIRlnivwN795o uIMA== X-Gm-Message-State: APjAAAUq+Guxmj8zSZDXN9jiIryw1+kdf5AVfd8i7BQz3kSMf3Qork3L TOEtFPuAXmdrkieaIJyis1QwqQ== X-Google-Smtp-Source: APXvYqworBWbKBupGoYQLzmTzDtgRlwubPNhGFLMZbZP2ydIdzH2M+7GwSC53JqdARLKpq8S/DJC8w== X-Received: by 2002:a5b:747:: with SMTP id s7mr13441933ybq.217.1576339190965; Sat, 14 Dec 2019 07:59:50 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: unreproducible bug with ${=...} From: dana In-Reply-To: <20191214045330.ehxgsufhhphg3twv@localhost> Date: Sat, 14 Dec 2019 09:59:49 -0600 Cc: Zsh Workers List Content-Transfer-Encoding: 7bit Message-Id: <5A850345-D71E-4CA9-967E-967CE6159A43@dana.is> References: <20191214045330.ehxgsufhhphg3twv@localhost> To: frederik@ofb.net X-Mailer: Apple Mail (2.3445.104.11) On 13 Dec 2019, at 22:53, frederik@ofb.net 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