From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 483 invoked by alias); 8 Oct 2015 19:22:42 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 20712 Received: (qmail 12161 invoked from network); 8 Oct 2015 19:22:41 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.0 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version:content-type; bh=QODlJMkimFmDFkrpjSBIdz5Sx5F20h13vXqjBE8WUoo=; b=ld1DvVPsol+MlKOm/MfovLjZdmHq8A827Q7nOQ8OF8QFha0yXQhCyyCnv8hU6LA3k8 WMSa+gRxUo7k/qJ6BuIv7QBncXWnNe5GNY1u0IbGtO4+/zh+yxil/DSIlWd/qym/CvTx +Vm0OaJIEcMjIxKQcxvnuq5GKPnb7KVKehE/9XUaevuSzFuY46AZAeOZ/+7lxoorCJg6 eR7kaWQHiZb9lzUHMmeSR8wegzwY0DrNzzGceel/12i4h+eIxnunSDgGi/1LGNHXoZi9 ybElc++KtXDlwpvPko3U1hcFXn4qjyhp48lJt5lXScp+L59tMSVM6MG5hVspn2AjxbO5 OpKg== X-Gm-Message-State: ALoCoQneEY5i80WtxAOKjG5ZxMPs9Zq6Q/dO9thMZF6BM7N5FUMRUIVjppkkrRK01nLJU1SDbIH5 X-Received: by 10.202.90.84 with SMTP id o81mr5517953oib.38.1444332159772; Thu, 08 Oct 2015 12:22:39 -0700 (PDT) From: Bart Schaefer Message-Id: <151008122236.ZM4177@torch.brasslantern.com> Date: Thu, 8 Oct 2015 12:22:36 -0700 In-Reply-To: <5616AB69.8080706@eastlink.ca> Comments: In reply to Ray Andrews "not an error?" (Oct 8, 10:44am) References: <20151008102315.0136766a@pwslap01u.europe.root.pri> <151008094643.ZM4110@torch.brasslantern.com> <5616AB69.8080706@eastlink.ca> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-users@zsh.org Subject: Re: not an error? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Oct 8, 10:44am, Ray Andrews wrote: } } print -rl "${(@k)aliases}}" } } Shouldn't the parser complain about the extra '}'? Why would it? You've put it in double quotes, so this is the same situation as print -rl "}" } certainly complains about too many opening '{', tho. Consider print -rl "{${(@k)aliases}}" print -rl "${(@k)aliases}{}" print -rl "${(@k)aliases}}{" Given the quotes, the only reason too many open braces is a problem is when you are inside the syntax of ${...} where braces are significant. As soon as a matching close-brace is found, double-quote context is active again and braces cease to have meaning.