Re: completion after ../

Re: completion after ../

[Sven Wischnowsky]

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@informatik.hu-berlin.de

Re: completion after ../

[Tanaka Akira]

In article <200001191618.RAA15845@beta.informatik.hu-berlin.de>,
  Sven Wischnowsky <wischnow@informatik.hu-berlin.de> writes:

> 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...)

Hm.  In general, I don't want to complete a directory which is already
described in the word, with first <TAB> at least.  Most frequently
happened example is X/../Z where X/../Z is X.
-- 
Tanaka Akira

Re: completion after ../

[Tanaka Akira]

In article <rsqwvp5ucjx.fsf@crane.jaist.ac.jp>,
  Tanaka Akira <akr@jaist.ac.jp> writes:

> Hm.  In general, I don't want to complete a directory which is already
> described in the word, with first <TAB> at least.  Most frequently
> happened example is X/../Z where X/../Z is X.

I rethought the problem and I found another idea to describe it: A
directory which shouldn't complete with first <TAB> is the directory
which go back path.  Of course, this is subset of previous idea but
it's enough for me.  The directory X/Y/Z is a such directory iff [[ X
-ef X/Y/Z ]] where Y and Z contains no `/'.  Note that if there is no
symlinks and in completion context, this happens only when Y == `..'.
-- 
Tanaka Akira

completion after ../

[Tanaka Akira]

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 `..'.
-- 
Tanaka Akira