From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17581 invoked by alias); 9 Dec 2015 10:00:16 -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: 37360 Received: (qmail 12428 invoked from network); 9 Dec 2015 10:00:15 -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: cbfec7f4-f79026d00000418a-6a-5667fbaa32f8 Date: Wed, 09 Dec 2015 10:00:08 +0000 From: Peter Stephenson To: Zsh hackers list Subject: Re: ZSH - tab-completion of $PATH won't work with /./ or /../ in it Message-id: <20151209100008.2377af37@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+NgFrrELMWRmVeSWpSXmKPExsVy+t/xK7qrfqeHGTT+1bc42PyQyYHRY9XB D0wBjFFcNimpOZllqUX6dglcGYu+7GIvmMRS8e59K2sD4yLmLkZODgkBE4n+3nnsELaYxIV7 69m6GLk4hASWMkp83XuUEcKZwSSx9f0tKOc0o8Tzlg+sEM4ZRomujY2sIP0sAqoSD57NBpvF JmAoMXXTbEYQW0RAS2LHyZNMILawgI9E79EHYDW8AvYSs/sWg9mcAsES/5Y3s0AMnckosfr4 WrAGfgF9iat/PzFBHGgvMfPKGUaIZkGJH5PvsYDYzEALNm9rYoWw5SU2r3kL9pyQgLrEjbu7 2ScwCs9C0jILScssJC0LGJlXMYqmliYXFCel5xrqFSfmFpfmpesl5+duYoSE9JcdjIuPWR1i FOBgVOLhveCSHibEmlhWXJl7iFGCg1lJhNf2C1CINyWxsiq1KD++qDQntfgQozQHi5I479xd 70OEBNITS1KzU1MLUotgskwcnFINjOWLg9oS7e+IMV5co33Bw+1a4c2C22mioVz746Tl76UZ Kext7u4uMHYvPZh79/i2S4JP2iLuTVos/IPjXPzClYs+/trOeXvalsOVYVtOLZB5dHCa/TwO ya/bfhnO32mrKpz346jN3aANGxTOaNoKPnrzYJawwtuyCQ1ZAbx2u9hd3kzZU3Ho53wlluKM REMt5qLiRADukbsKZQIAAA== On Tue, 08 Dec 2015 22:22:36 -0800 Bart Schaefer wrote: > On Tue, Dec 8, 2015 at 9:24 PM, John Polansky wrote: > > > > While I realize it's unusual to have . or .. in a path.. it can happen > > through scripting and to me this seems like a bug which should be fixed. > > The command hash table has NEVER included commands that appear along > any relative path. You can rationalise your path simply enough in one of your start-up files: path=(${path:a}) pws