From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8148 invoked by alias); 15 Aug 2014 08:42:09 -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: 33016 Received: (qmail 16218 invoked from network); 15 Aug 2014 08:42:08 -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=-6.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI, SPF_HELO_PASS autolearn=ham version=3.3.2 X-AuditID: cbfec7f4-b7f156d0000063c7-b5-53edc7de9668 Date: Fri, 15 Aug 2014 09:42:05 +0100 From: Peter Stephenson To: Zsh workers Subject: Re: PATCH: completion utility function for lists Message-id: <20140815094205.144c9dc3@pwslap01u.europe.root.pri> In-reply-to: <140814215418.ZM4199@torch.brasslantern.com> References: <28890.1407967194@thecus.kiddle.eu> <140814215418.ZM4199@torch.brasslantern.com> 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+NgFupiluLIzCtJLcpLzFFi42I5/e/4Vd17x98GG+zuFrQ42PyQyYHRY9XB D0wBjFFcNimpOZllqUX6dglcGTfev2Ur+MhScWuORwPjF+YuRk4OCQETibWvrrBB2GISF+6t B7K5OIQEljJKtG76ygzhLGeS6Nn2jRGkikVAVeL9gvtgNpuAocTUTbPBbBGg+JwTp1i7GDk4 hAUsJRpuJoGYvAL2EvuPsoJUcAJFl6/8xA5iCwnESZya9ABsL7+AvsTVv5+YIG6wl5h55QzY RF4BQYkfk++xgNjMAloSm7c1sULY8hKb17xlnsAoMAtJ2SwkZbOQlC1gZF7FKJpamlxQnJSe a6hXnJhbXJqXrpecn7uJERJ+X3YwLj5mdYhRgINRiYf3QdjbYCHWxLLiytxDjBIczEoivElz gUK8KYmVValF+fFFpTmpxYcYmTg4pRoYBQzsbyau7/JwY2Vx/pm/e9ki7eBtDhd1Py9Lr325 Ky1r6Rwe9Yq3jXrJ8juXMjy3ebFzuolY9qcux4dHjgTk3H2Zf/Ol0oNwz76bF51FdnY8dzLe fOxa0YY3ky79OVcVxzL1cu7beybyF8OrmLzKP/UtcizYtaJhh3nNvNvmH+q6JR7LfVtyTIml OCPRUIu5qDgRACxc+BwdAgAA On Thu, 14 Aug 2014 21:54:18 -0700 Bart Schaefer wrote: > Preliminary question: I noticed these changes got committed/pushed. Are > we rushing this in before the release for some reason, or will the release > be made off an older tag (in which case we'll need to branch (?) to put > in any patch for the "cd /" warning issue)? I'm not branching. I tend not to worry about new functions since they shouldn't break anything, in theory. I see it's going to have knock-on effects on completion functions, so ideally ought to wait, but it's not worth doing anything special now. pws