From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7270 invoked by alias); 7 Mar 2013 10:33:02 -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: 17672 Received: (qmail 18303 invoked from network); 7 Mar 2013 10:32:59 -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 Received-SPF: none (ns1.primenet.com.au: domain at samsung.com does not designate permitted sender hosts) X-AuditID: cbfec7f5-b7fd76d000007247-ef-51386a7cc864 Date: Thu, 07 Mar 2013 10:22:51 +0000 From: Peter Stephenson To: zsh-users@zsh.org Subject: Re: Slow completion Message-id: <20130307102251.4ff2e611@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+NgFupkluLIzCtJLcpLzFFi42I5/e/4Fd2aLItAg0NPWCx2nFzJ6MDoserg B6YAxigum5TUnMyy1CJ9uwSujIVfSgsec1e8va3RwLiGs4uRk0NCwETi1dG5TBC2mMSFe+vZ uhi5OIQEljJKvHv4hhnKYZK48rebEaSKRUBV4tOuX8wgNpuAocTUTbPB4iICohLLV2xm72Lk 4BAWkJE4OoUFJMwrYC/xaUc/K0iYU0BTYmaPA0hYSEBD4seUz+wgNr+AvsTVv5+gbrCXmHnl DCNEq6DEj8n3wMYwC2hJbN7WxAphy0tsXvOWeQKjwCwkZbOQlM1CUraAkXkVo2hqaXJBcVJ6 rpFecWJucWleul5yfu4mRkjwfd3BuPSY1SFGAQ5GJR7ejTnmgUKsiWXFlbmHGCU4mJVEeC/I WQQK8aYkVlalFuXHF5XmpBYfYmTi4JRqYKzyTH3TYM7/5mbWqy6Du+pn1CQKlb+vCa72Mem/ 9GvxpZ1rX9z9s46170vPtOP9d/mmFTTzRyT/nHSY/1ux7CsmhkMHYl2i2Gw6V/WYTzf6OUsp /u2WT8blt6oVrurYNLbGb1hyu0U/cuKSzE+t9+drrT5lUmF/m93gqkzQXcFW7nyTqKV5E5VY ijMSDbWYi4oTAd8dDsAcAgAA On Wed, 06 Mar 2013 22:40:41 +0100 Thorsten Kampe wrote: > Zsh completion has always been kind of slow for me (in comparison to > bash) but I always contributed this to the superior functionality (my > .zshrc is two and a half times as long as my .bashrc). > > Today I decided that it had become unbearable and started investigating. > > I tested a simple completion like > > /usr/bin/cadaver.exe > > The directory completion (usr and bin) was already slow but the > executable (cadaver.exe) took ages. > > 1. Testing revealed that "setopt path_dirs" was responsible for the slow > directory completion. > > The zshoptions manual page says that path_dirs should not apply in the > above case[1] but a Process Monitor log showed that Zsh was actually > searching through the whole executable path. It's doing completion equivalent to: /usr*/bin*/cada* when you hit TAB in the last case. This is a feature, but definitely annoying in the case where path completion is slow. You can turn it off for the case where the directories exist by setting the style accept-exact-dirs to true: I've been doing this under Cygwin. In other words, this should complete /usr/bin/cadaver.exe faster the way you're doing it, since it's one component at a time, but still allows you to complete /u/b/c in one go. I don't think we have an option to turn completion of all path segments off altogether at the moment. pws