Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com X-Envelope-Sender-Is: Andrej DOT Borsenkow AT mow DOT siemens DOT ru (at relayer david.siemens.de) Date: Sun, 8 Jul 2001 21:07:33 +0400 (MSD) From: Andrej Borsenkow X-X-Sender: To: Michael Schaap cc: , ZSH Workers Mailing List Subject: RE: Zsh observations In-Reply-To: <5.1.0.14.2.20010708145207.0271f560@imap.local.mscha.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Sun, 8 Jul 2001, Michael Schaap wrote: > If I'm trying to complete an executable in the current directory, e.g. > % setu > it will give me neither "setup", nor "setup.exe". This is logical, because > the special .exe handling is only for the PATH hash. > > Would you know a workaround for that? > Ehh ... path=($path .) It completes only commands in path; that is correct and expected. Do you mean, that under Cygwin local directory is always implicitly in path (it is in DOS)? > > (Wouldn't it be nice if Cygwin did this foo.exe -> foo handling > automagically for us?) > What do you mean exactly? Zsh hashes path by calling readdir(). I do *not* want readdir return foo if real file name is foo.exe. There is nothing Cygwin can do (at least, I cannot think of anything). May be in case of foo.exe we should not hash foo.exe but just foo. That seems logical. -andrej -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/