From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4588 invoked from network); 19 Jan 2000 16:19:04 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 19 Jan 2000 16:19:04 -0000 Received: (qmail 6322 invoked by alias); 19 Jan 2000 16:18:53 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 9372 Received: (qmail 6315 invoked from network); 19 Jan 2000 16:18:52 -0000 Date: Wed, 19 Jan 2000 17:18:49 +0100 (MET) Message-Id: <200001191618.RAA15845@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.auc.dk In-reply-to: Tanaka Akira's message of 19 Jan 2000 18:51:44 +0900 Subject: Re: completion after ../ Tanaka Akira wrote: > Sometimes completion after ../ frustrates me. > > For example: > > Z:akr@crane% mkdir -p z/tstdir > Z:akr@crane% cd z/tstdir > Z:akr@crane% ls .. > tstdir > Z:akr@crane% ls ../ > > -> > > Z:akr@crane% ls ../tstdir/ > > Since there is only one caondidate `tstdir', zsh completes it. It is > consistent behaviour. But I want to list instead of completion > because ../tstdir is not useful --- it's current working directory. > > I think it is useful that a style to control this behaviour: list > files even if there is only one completion candidate when previous > path component is `..'. Only with `..'? What I'm after is: can someone come up with a good description of how exactly we would want this? (I already stumbled over the same example Tanaka described, too, but I have the feeling that this might be only one case of a more general thing...) Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de