From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24229 invoked by alias); 19 Jun 2015 18:40:17 -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: 35533 Received: (qmail 11326 invoked from network); 19 Jun 2015 18:40:14 -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=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H2 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=qe+0gyjpUE5xPAzz5hWeRsL+KINNo8iObL24hpJ/dww=; b=GfzDxFtJnzNy+FsKvwHp5Afj+fuWm/wBN3n4rtCjNDtnzQmZOw6Y0L8GAyifuwTChK TBrfmcReYnL8XRph4j9ZMJvO5mKZ1GHW6ODQFkVf+si43Ob1x0FbRUpb1AWLkSQ03B+8 Ci2zSnaMboxfTLp1eEQjFmiQwFv/uegQz+6El92xPa8+N0/yGQXShHl4tLSppMNswZ4O AJWajZFQdLq7On+0akF/ETBZEH+NdyAi6roNANy23mkRoBLNq/JfEsIVr8OVx+2+iJNy 3KCzVHBUvU2iTnNq+949fdoxoVKXUptUb8zUtALhk/n6kPyw5KkkN0SiE+o/7Tr12VR7 su+w== X-Gm-Message-State: ALoCoQkKvNgwdn462ryFtimsgSvs2j0mAcJtvV1zFkVAguJ41nOrQJdmAglB18n6xsbw9BBzZyi/ X-Received: by 10.182.128.234 with SMTP id nr10mr14874067obb.81.1434739212683; Fri, 19 Jun 2015 11:40:12 -0700 (PDT) From: Bart Schaefer Message-Id: <150619114009.ZM4265@torch.brasslantern.com> Date: Fri, 19 Jun 2015 11:40:09 -0700 In-Reply-To: <7337.1434735386@thecus.kiddle.eu> Comments: In reply to Oliver Kiddle "Re: Typeset with array" (Jun 19, 7:36pm) References: <5578996E.3080700@thequod.de> <150610191427.ZM30841@torch.brasslantern.com> <5579C247.1060800@thequod.de> <150611183639.ZM32247@torch.brasslantern.com> <20150612094237.338f79d5@pwslap01u.europe.root.pri> <20150619123930.2688d9e3@pwslap01u.europe.root.pri> <7337.1434735386@thecus.kiddle.eu> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: "Zsh Hackers' List" Subject: Re: Typeset with array MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Jun 19, 7:36pm, Oliver Kiddle wrote: } } Is there a reason why noglob can't precede assignments. That could be } useful. The most obvious reason is that noglob is a precommand modifier, which quite literally means the parser is looking for a command to follow it and doesn't find one. It's the same reason that "exec x=foo" doesn't work, although zsh doesn't discover that "x=foo" is not a command until the parent shell has already committed to exiting (in bash, an interactive shell returns to the prompt on "exec command-that-does-not-exist"). On the other hand nocorrect is allowed to appear before assignments, so there probably isn't any overriding reason that noglob can't be also, other than that nocorrect is a reserved word and noglob is not.