From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25037 invoked by alias); 20 Apr 2017 14:55:55 -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: X-Seq: 40991 Received: (qmail 1928 invoked from network); 20 Apr 2017 14:55:54 -0000 X-Qmail-Scanner-Diagnostics: from mail-ua0-f176.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(209.85.217.176):SA:0(-2.8/5.0):. Processed in 1.366562 secs); 20 Apr 2017 14:55:54 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.8 required=5.0 tests=RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,SPF_PASS,T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: schaefer@brasslantern.com 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.217.176 as permitted sender) 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=zbP/Ki2c5HMgOTC9h24MLT49EAEuQ+WMUYe+jKrqtYs=; b=u30qxqIP+ZY/OzzUeRCCIScGZzgH0yRPIqcnOZCIRJuDLQ+ah1L0cS+jcNbwRdepQu dZsvx9ztLHB0ENVimUSnha/Xa+jLgcCHEUlqhpQDESdAIEfNKXJOjIYnv54+ehUjIgxR cxD0lKgRW9mbKluBaaNDlVRdNc70PhwZaXCndsU84Yb/EkKO3t4f4yQQVSkSL6s/pBPB MqkAJxPCCiE8pKIV0d1pTYR3FIgE4LqC1rnD6kw5duuSM78AE/2FAjAQLd9T8e0NcTpV a+psNCQCv6IMNUKswDuA1Zx098KhcO5cTtNdx07nnk0fjxuTHJrx852Op6A3Cl6yo8uv aXTw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version; bh=zbP/Ki2c5HMgOTC9h24MLT49EAEuQ+WMUYe+jKrqtYs=; b=GiwXDI90RWrFuzKKV7bOmfhYscrd2csoNrEqjKwjTwvHKCzOKrWkbTwQKNHHbS3wJv qfxzoPHcubpRyd0AzETWFO9DkUDyCiuJu2KQsA86u68ty/3GvEW35DdbW46/PwLQERqc neP3GzE7mJlbM/ibkxfzPVvoX3/PSFQGHanFcu9++Rd3BWqf9Bsqz2/ypAlRcTtifeYw XI2QZxBqEfZc8mq9Hy9IbffbPnWOB0IkdyYOPF0ugZ6YBVtd/c8Y2yP8ubBpSNMixRAd vHe6T68qvJaouEdEW4OqmmSxS145N3jFs/qKhDw96xuBDdAzEFSs0S9VRJqV1a1xkaEz lCfg== X-Gm-Message-State: AN3rC/5rY+AlIm54HRjlC0JNGQpG7WeKeG5UphMx0wV2ZWYi3nKcGKVV obAMx5u10SOVo51x X-Received: by 10.159.54.205 with SMTP id p71mr3721986uap.67.1492700146295; Thu, 20 Apr 2017 07:55:46 -0700 (PDT) From: Bart Schaefer Message-Id: <170420075621.ZM2340@torch.brasslantern.com> Date: Thu, 20 Apr 2017 07:56:20 -0700 In-Reply-To: <20170420112131.4ddbace7@pwslap01u.europe.root.pri> Comments: In reply to Peter Stephenson "Re: Colon-array variables can crash "sh" emulation" (Apr 20, 11:21am) References: <170414193104.ZM16289@torch.brasslantern.com> <20170420112131.4ddbace7@pwslap01u.europe.root.pri> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: Colon-array variables can crash "sh" emulation MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Apr 20, 11:21am, Peter Stephenson wrote: } } The only robust solution looks like being not let PATH's ename element } point at path. Otherwise the code following ename has to jump through } hoops to see if the parameters are "really" linked, which is far too } late. Yes. } The fly in the ointment here is that colonarrsetfn() refuses to fix up } the environment unless the ename element is set. It's not clear to me } why since I don't think ename can be unset for special tied variables } which are the only use of colonarrsetfn(). This is probably not be true any longer, but at one time I think "ename" was doing double duty as a flag that the parameter was in fact exported. My understanding was that it's called "ename" because it's the name in the environment to which the parameter refers. This is probably only the case for the array version of the parameter and not for the scalar, or something like that.