From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27469 invoked by alias); 11 Oct 2013 09:06:32 -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: 31814 Received: (qmail 347 invoked from network); 11 Oct 2013 09:06:27 -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: cbfec7f5-b7ef66d00000795a-d3-5257bd3525bb Date: Fri, 11 Oct 2013 09:56:20 +0100 From: Peter Stephenson To: zsh-workers@zsh.org Subject: Re: Bug: Completion of the 'zsh' command. Message-id: <20131011095620.224545de@pwslap01u.europe.root.pri> In-reply-to: <131010124113.ZM4512@torch.brasslantern.com> References: <525564FE.3030705@gmail.com> <131009200134.ZM3418@torch.brasslantern.com> <131010124113.ZM4512@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+NgFupjluLIzCtJLcpLzFFi42I5/e/4NV3TveFBBjNumlscbH7I5MDoserg B6YAxigum5TUnMyy1CJ9uwSujL4vO1gLOlkrpk04zdbAOImli5GTQ0LAROLdhmfMELaYxIV7 69m6GLk4hASWMkrcun2MBcJZziTxsm0nWBWLgKrEyV/LWUFsNgFDiambZjOC2CIC4hJn154H myosYCSx9dFjsHpeAXuJD78fgNmcApYSq3tWskIMbWOUOPrnIdggfgF9iat/PzFBnGEvMfPK GUaIZkGJH5PvgQ1lFtCS2LytiRXClpfYvOYt8wRGgVlIymYhKZuFpGwBI/MqRtHU0uSC4qT0 XCO94sTc4tK8dL3k/NxNjJAw/LqDcekxq0OMAhyMSjy8M0PCg4RYE8uKK3MPMUpwMCuJ8O6b DxTiTUmsrEotyo8vKs1JLT7EyMTBKdXAuG5m5cl9u8s/zw3V+C66c3lIe+qnnB9JLjx3Nk+/ GrVgt7zUsg+rov58Vk285s1xZWOz8vLirTFppgGnhR4nWxy7+U2a7/L7tul6WpKR62O/Xmxd 22B64la07blmfm/2Zc2Zr94edPOqzpgfqblVWe/RpPdipuZxCSwntkeF7X/8hUGP7dvUNUos xRmJhlrMRcWJALAvPLchAgAA On Thu, 10 Oct 2013 12:41:13 -0700 Bart Schaefer wrote: > (1) The patch I already sent, which assures that this call to _message > happens late enough for $compstate[nmatches] to be valid. Perhaps combining this with a note in compsys.yo about this side effect to _message and hence also of _arguments when displaying messages would cover enough bases. For _arguments the caveat is perhaps more what you said early --- that it doesn't espect to be combined arbitrarily with other forms of completion ("arbitrarily" because it does have ways of returning control to the caller to take the next steps). pws