From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5540 invoked from network); 29 Sep 2002 05:49:24 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 29 Sep 2002 05:49:24 -0000 Received: (qmail 11416 invoked by alias); 29 Sep 2002 05:49:19 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 17740 Received: (qmail 11404 invoked from network); 29 Sep 2002 05:49:18 -0000 Date: Sun, 29 Sep 2002 01:49:13 -0400 From: Clint Adams To: zsh-workers@sunsite.dk Subject: ../ in PATH and completion Message-ID: <20020929054913.GA29838@dman.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-Virus-Scanned: by amavisd-milter (http://amavis.org/) 1% mkdir /tmp/testdir /tmp/otherdir 2% touch /tmp/testdir/foobin 3% chmod 755 !$ 4% zsh A/1% PATH=/tmp/testdir A/2% fo (will offer foobin as a completion, and hash it) or B/1% PATH=/tmp/otherdir/../testdir B/2% fo (will not offer foobin, and not hash it) In contrast, bin_whence likes it just fine. C/1% PATH=/tmp/otherdir/../testdir C/2% which foobin /tmp/otherdir/../testdir/foobin C/3% hash -L hash foobin=/tmp/otherdir/../testdir/foobin Why the inconsistency?