Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: completion after ../
- X-seq: zsh-workers 9372
- From: Sven Wischnowsky <wischnow@xxxxxxxxxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxx
- Subject: Re: completion after ../
- Date: Wed, 19 Jan 2000 17:18:49 +0100 (MET)
- In-reply-to: Tanaka Akira's message of 19 Jan 2000 18:51:44 +0900
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
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 ../<TAB>
>
> ->
>
> 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@xxxxxxxxxxxxxxxxxxxxxxx
Messages sorted by:
Reverse Date,
Date,
Thread,
Author