From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-37355-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 27733 invoked by alias); 9 Dec 2015 05:25:34 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 37355
Received: (qmail 16492 invoked from network); 9 Dec 2015 05:25:33 -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,FREEMAIL_FROM,
	HTML_MESSAGE,T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.0
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:from:date:message-id:subject:to:content-type;
        bh=Q0oyGVtAe60RGcbWMDgy3BDPFjhNGY6ppp+0LnHw3/k=;
        b=BwowrpIQGMNAjUzA3UuvkBcAHheJKOuB1z/6tWPJoBZO3JM4mnkyPMWlo44Df7Bzqs
         j+4vmcuZaJ6tbkuXhPuszLXjhIy03dswybWbbZsLBKBFAnxvx+KOhYdNXyCWUwRNf2Dl
         NEyd+IYQFSCWxw2mHAe3nXc7VbqtAWVPoGLfCVHHwAh2vtZZbjM6kDwl/aGrSqHXXuhc
         jMw+PgCfz/a5rwv0zbD/UdYD7jd5NtD8UZyfIZ7FCKfsC7qwOnsk1QFz9awuS8ktdeFk
         5seDMfcZfv0xEAJle5qMkmcpTyUEbhQrzxuy4wShz/k66oCJcjKvmd9Nb0O5bugK7gcK
         Jw0A==
X-Received: by 10.182.176.102 with SMTP id ch6mr2713614obc.31.1449638729459;
 Tue, 08 Dec 2015 21:25:29 -0800 (PST)
MIME-Version: 1.0
From: John Polansky <johnpolansky@gmail.com>
Date: Tue, 8 Dec 2015 23:24:49 -0600
Message-ID: <CAKKoV8-uEhgRxL_9byx+7OHzgTiqYTT5LSyGmcAZowR4GeJFZA@mail.gmail.com>
Subject: ZSH - tab-completion of $PATH won't work with /./ or /../ in it
To: zsh-workers@zsh.org
Content-Type: multipart/alternative; boundary=e89a8ff1cd3685ad560526705147

--e89a8ff1cd3685ad560526705147
Content-Type: text/plain; charset=UTF-8

I've noticed a bug in:

 zsh --version
zsh 5.2 (x86_64-apple-darwin15.0.0)

It drove me up the wall before I realized but it appears if in your $PATH
variable you have a path that contains /./ or /../ the tab-completion for
commands will not search that directory.

For example

*export PATH=/Users/jpolansky/test*
which has a command *cmd_test* in it with +x permissions.

$ cmd<tab>
-- it finds cmd_test

But if you have:
*export PATH=/Users/jpolansky/./test*
*or*
*export PATH=/Users/jpolansky/../test*

*#cmd<tab>*
-- fails to find cmd_test

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.
Hopefully you will agree.

John

--e89a8ff1cd3685ad560526705147--