From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14164 invoked by alias); 25 Nov 2015 10:00:44 -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: 20989 Received: (qmail 29123 invoked from network); 25 Nov 2015 10:00:43 -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-AuditID: cbfec7f5-f79b16d000005389-ba-565586c78d18 Date: Wed, 25 Nov 2015 10:00:36 +0000 From: Peter Stephenson To: =?UTF-8?B?TmfDtA==?= Huy , Zsh Users Cc: Cuong Manh Le Subject: Re: [Zsh bug] function define bug Message-id: <20151125100036.69e8ec60@pwslap01u.europe.root.pri> In-reply-to: References: Organization: Samsung Cambridge Solution Centre X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu) MIME-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrILMWRmVeSWpSXmKPExsVy+t/xa7rH20LDDDYtkLCYtGMJs8WMSTdZ LXacXMnowOyxc9Zddo9FE3tYPFYd/MAUwBzFZZOSmpNZllqkb5fAlXF5+mX2guPMFTPmhTQw vmLqYuTkkBAwkehfsZ4dwhaTuHBvPVsXIxeHkMBSRonWqQcZIZwGJokbd95DZc4xSsza9Y8V wjnLKPHk90xWkH4WAVWJ7qev2UBsNgFDiambZjOC2CICoRKbrpxjAbGZBXQlWm63gO0TFtCS uH/zKdgdvAL2EgePrQCr4RQIlljatBVq9R9miQlTH4EV8QvoS1z9+wnqcHuJmVfOMEI0C0r8 mHwPaoGWxOZtTawQtrzE5jVvmUFsIQF1iRt3d7NPYBSZhaRlFpKWWUhaFjAyr2IUTS1NLihO Ss810itOzC0uzUvXS87P3cQIiYivOxiXHrM6xCjAwajEw/viSUiYEGtiWXFl7iFGCQ5mJRHe 37WhYUK8KYmVValF+fFFpTmpxYcYpTlYlMR5Z+56HyIkkJ5YkpqdmlqQWgSTZeLglGpgZNUp 9nO/sV1y7vfNj11uyAQfO2X4ay5XtF/7z58n/Vg8oxzui0yYnCXxu8aprmxdlJuU+UvOeSo/ /y2dwLiZc8eRczVmulFn/jT7Jk6/yfWgwNGp94leuLtocQ5njNF+v4A4Ma4s3VhFD74vX1Y2 7PtrJxnoEDlBu3Drib+vdzKtEMg4XzNHiaU4I9FQi7moOBEA6WCzo4QCAAA= The MULTI_FUNC_DEF behaviour was there in the shell from the start (and didn't used to be optional) --- I think it was there mostly for defining multiple trap functions in one go. That's about the only standard use, anyway (there was one instance in the completion code until we removed it). Feel absolutely free to turn it otf yourself, but please can we stop the yes we should / no we shouldn't unless you have new information. Thanks pws