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.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FROM,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 c2cee978 for ; Wed, 14 Aug 2019 09:38:37 +0000 (UTC) Received: (qmail 13921 invoked by alias); 14 Aug 2019 09:38:27 -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: 44661 Received: (qmail 12752 invoked by uid 1010); 14 Aug 2019 09:38:27 -0000 X-Qmail-Scanner-Diagnostics: from mail-wr1-f50.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.101.2/25538. spamassassin: 3.4.2. Clear:RC:0(209.85.221.50):SA:0(-2.0/5.0):. Processed in 1.705006 secs); 14 Aug 2019 09:38:27 -0000 X-Envelope-From: stephane.chazelas@gmail.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.221.50 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=I/t5oophQ9BuqNf7wQz+xxq0Tjx4+gt1aMMEPj+A/Cg=; b=XoKsg2KOTYYrwnbyRvSqFM8ATNBP8hNIBlGNRmtlitktlvn2LjisrqnvVGZRx0nBB6 Vts58EgCB21kOQwtE5aQl69QBIHSdNAvNKuRcvJlZc8Gq8AKO1RHgF+7hIj5tzh4uEMt GB0Jc6nScBoNnH1ypFSFMMQdgNjs16jllQT2gqLZKzmV6szofaUDM3bscnv5t698D11Z 76VQ9VrWKl1apcKiidqAcbQK+0EQqVUHYOezolsfYKkSSQ3vBdjrMDdq1+r5rVj6dGmr +I7St4nxYSwb9jVkI4T7eKXruKmXVtVSGFCPhO8NhPVKBTgYoJmJ0/IZI9YQ/u0RUvGb gPSg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=I/t5oophQ9BuqNf7wQz+xxq0Tjx4+gt1aMMEPj+A/Cg=; b=fL26uguXGMBtPG+KBhW1RbST6x5zokrDuE4W1M7Jh2ZG4TKFuKOcn3OpOWJU93nI7/ mMoOxYZOurS79ty9kKmKcc1NTdGOhdHeL/NwDD60XsHFX07GUD7mhsTSrXwDKGg36PN3 tEVphsT3z/xeK+zBX9P6JIH/x4GWaF2b8owJjATIKSGXpDEUdZJWrS8zVuPIeTJXkH7L iurKT9rf297grN64HuZyyuIzJkpYaygLCtSTYvrnEBCJai+9MMyrKoy0QSSZ6oUPD04w cv+gO3izxGqpr/EA6TQD1nxBVz9IjQMYdxGwHtsc7quNmwzXy3i1eSPjgCNEJZV1k6Ed twfw== X-Gm-Message-State: APjAAAXWyl0Uc2s+hf38G+cpgADNu/mt6A1Rm1sj59mmyvydW7pOZ60Y mV4ZnWHg1cK8+Gqt3VkHD1M= X-Google-Smtp-Source: APXvYqyCO9SmfECcr2RZu4iW8hIFV772m42Cn9PniuP7C3JOjeQLmtUhxeS175Uh2WNIBjaAEdC81w== X-Received: by 2002:adf:ef05:: with SMTP id e5mr34908158wro.158.1565775470378; Wed, 14 Aug 2019 02:37:50 -0700 (PDT) Date: Wed, 14 Aug 2019 10:37:48 +0100 From: Stephane Chazelas To: Aryn Starr Cc: zsh-workers@zsh.org Subject: Re: Bug Report: Variable becomes unset without reason Message-ID: <20190814093748.u3pkdzrixmtunnt7@chaz.gmail.com> Mail-Followup-To: Aryn Starr , zsh-workers@zsh.org References: <2154283D-97B8-436B-8CC5-40624C11F356@icloud.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2154283D-97B8-436B-8CC5-40624C11F356@icloud.com> User-Agent: NeoMutt/20171215 2019-08-08 20:38:05 +0430, Aryn Starr: > I have included the file that reproduces the bug with `zsh -f` and the result of running it in https://gist.github.com/NightMachinary/32689e786a3b7f5865a042d49b884b57 . Please try and make sure your bug reports are self-contained. The zsh ML has been around for decades and along with its archives will probably be around for several more decades, but we can't tell much about github (that link may become invalid at any time). We should also not have to fire up a web browser to figure out what the bug is about. Now, that being said, as discussed on U&L it looks like a bug indeed and a shorter reproducer is: $ zsh -xc 'v=1; f() { local v; v=2 true; }; f; typeset -p v' +zsh:1> v=1 +zsh:1> f +f:0> local v +f:0> v=2 +f:0> true +zsh:1> typeset -p v zsh:typeset:1: no such variable: v Most likely, that's the "v=2 true" (where "true" is a builtin) that ends up unsetting the "v" from the global scope. -- Stephane