From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18760 invoked by alias); 4 Dec 2013 07:27:29 -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: 18196 Received: (qmail 9536 invoked from network); 4 Dec 2013 07:27:13 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 From: Bart Schaefer Message-id: <131203232722.ZM30313@torch.brasslantern.com> Date: Tue, 03 Dec 2013 23:27:22 -0800 In-reply-to: Comments: In reply to danielwallace "RE: Processing Arguments" (Dec 3, 4:49pm) References: X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: Zsh-Users List Subject: Re: Processing Arguments MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Dec 3, 4:49pm, danielwallace wrote: } } Try looking up zparseopts. It is along the same lines as bush's getopts. Is "bush" a typo, or yet another shell I've never heard of? zsh has "getopts" as well as "zparseopts". The syntax of zparseopts is a bit harder to understand, but it loops over the entire argument list for you and stuffs values into arrays or associative arrays, whereas with getopts you write your own loop (usually "while getopts ...").