From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22415 invoked by alias); 15 Feb 2014 08:38:07 -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: 18460 Received: (qmail 5268 invoked from network); 15 Feb 2014 08:37:51 -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: <140215003759.ZM25986@torch.brasslantern.com> Date: Sat, 15 Feb 2014 00:37:59 -0800 In-reply-to: Comments: In reply to Sebastian Stark "Re: zparseopts default associative array" (Feb 14, 8:55am) References: <140213085618.ZM26934@torch.brasslantern.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-users@zsh.org Subject: Re: zparseopts default associative array MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Feb 14, 8:55am, Sebastian Stark wrote: } } Thanks for your very helpful answer. Is there any chance this gets } implemented one day or do I have to find a workaround? You should probably find a workaround anyway, because there will be versions of zsh floating around for years that have the old behavior.