X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org X-Spam-Score: -85.377 Message-ID: <493ECBA4.4010704@sh.cvut.cz> Date: Tue, 09 Dec 2008 20:48:52 +0100 From: =?UTF-8?B?VsOhY2xhdiBIYWlzbWFu?= User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: ZSH completion problem References: <493EB6B8 DOT 2070501 AT sh DOT cvut DOT cz> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Peter A. Castro wrote, On 9.12.2008 20:39: > On Tue, 9 Dec 2008, V�clav Haisman wrote: > > Hi, > >> Greetings, Výclav, > > I have just updated ZSH and now when completing paths it prints the > following: > _alternative:69: command not found: _path_commands > >> That's a different symptom than what other people has reported. >> But, it could just be from a stale dump file. > >> If you haven't already done so, please remove your .zcompdump (or >> whatever custom dump file you might be using) and re-generate it. > >> The best way to do this cleanly is to comment out running 'compinit' from >> your .zsh* files, exit and start a fresh zsh, then run compinit (answer >> yes if it complains about insecure dirs). Check that .zcompdump is more >> than 256 bytes (should be about 33k). If it's too small, run >> compinit -d .zcompdump >> Check .zcompdump again. If it's still too small, try exiting and >> re-starting the shell again and run compinit -d again. > >> Then you can uncommment running compinit from your .zsh* files >> (you might need to add the '-i' option) and things should be good. > >> One caveat is that DOS style paths (eg: "C:/") do not seem to tab >> complete right now. It's a know problem that I'm trying to track down. >> Let me know if there are other issues. Hi, thanks, it was the stale .zcompdump file. - -- VH -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) iFYEAREIAAYFAkk+y6MACgkQhQBMvHf/WHliwgDeMB/7Yko4g4ClhFzO6zcHEsXe 5vx6udH8ED6EtwDdGkbBjb70i/wvJpX/gYyv1IcdWFdaEXlZEkJnbQ== =aZXA -----END PGP SIGNATURE----- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/