From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5522 invoked by alias); 6 Sep 2013 06:13:17 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 31704 Received: (qmail 26535 invoked from network); 6 Sep 2013 06:13:11 -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=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 Received-SPF: none (ns1.primenet.com.au: domain at closedmail.com does not designate permitted sender hosts) From: Bart Schaefer Message-id: <130905231336.ZM30256@torch.brasslantern.com> Date: Thu, 05 Sep 2013 23:13:36 -0700 In-reply-to: Comments: In reply to Jan Larres "Re: Directory completion acts as if CHASE_LINKS is set" (Sep 6, 1:42pm) References: <130905083139.ZM29859@torch.brasslantern.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: Directory completion acts as if CHASE_LINKS is set MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Sep 6, 1:42pm, Jan Larres wrote: } Subject: Re: Directory completion acts as if CHASE_LINKS is set } } On 06/09/13 03:31, Bart Schaefer wrote: } > In any case, this is a problem inherent in the way globbing interprets } > "../" -- filename generation does not obey the same rules as "cd" path } > resolution. } } Thanks, that patch does solve the issue with cd to a certain degree. But } as you said yourself it is not specific to cd - for example, 'ls ../[TAB]' } has the same problem. No, you misunderstand. It actually *is* specific to cd -- ls is an external command and will physically follow ../, so it is correct for completion for ls to do so as well. Only in shell builtins can ../ refer to $PWD:h/, and the only builtins that have this behavior are cd and pushd.