* completion after ../
@ 2000-01-19 9:51 Tanaka Akira
2000-01-19 11:17 ` completion after // Alexandre Duret-Lutz
0 siblings, 1 reply; 5+ messages in thread
From: Tanaka Akira @ 2000-01-19 9:51 UTC (permalink / raw)
To: zsh-workers
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* completion after //
2000-01-19 9:51 completion after ../ Tanaka Akira
@ 2000-01-19 11:17 ` Alexandre Duret-Lutz
0 siblings, 0 replies; 5+ messages in thread
From: Alexandre Duret-Lutz @ 2000-01-19 11:17 UTC (permalink / raw)
To: zsh-workers
>>> "Tanaka" == Tanaka Akira <akr@jaist.ac.jp> writes:
Tanaka> Sometimes completion after ../ frustrates me.
[...]
Along with the same lines, something I don't like is
that the path `a///////b' is not understand as 'a/b' by _path_files
(when I cut and past path names that contains doubled
slashes, it's annoying to not be able to complete after these).
I wanted to add :
# Squeeze sequences of slashes
PREFIX="${PREFIX//(\\/)#//}"
SUFFIX="${SUFFIX//(\\/)#//}"
[[ $PREFIX = */ ]] && SUFFIX=${SUFFIX#/}
at the beginning of _path_files, but then realized that
people may want to use `//' to do partial path completion.
Should this be tunable ?
--
Alexandre Duret-Lutz
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: completion after ../
2000-01-19 18:44 ` Tanaka Akira
@ 2000-01-20 4:34 ` Tanaka Akira
0 siblings, 0 replies; 5+ messages in thread
From: Tanaka Akira @ 2000-01-20 4:34 UTC (permalink / raw)
To: zsh-workers
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: completion after ../
2000-01-19 16:18 completion after ../ Sven Wischnowsky
@ 2000-01-19 18:44 ` Tanaka Akira
2000-01-20 4:34 ` Tanaka Akira
0 siblings, 1 reply; 5+ messages in thread
From: Tanaka Akira @ 2000-01-19 18:44 UTC (permalink / raw)
To: zsh-workers
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: completion after ../
@ 2000-01-19 16:18 Sven Wischnowsky
2000-01-19 18:44 ` Tanaka Akira
0 siblings, 1 reply; 5+ messages in thread
From: Sven Wischnowsky @ 2000-01-19 16:18 UTC (permalink / raw)
To: zsh-workers
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
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2000-01-20 4:35 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-01-19 9:51 completion after ../ Tanaka Akira
2000-01-19 11:17 ` completion after // Alexandre Duret-Lutz
2000-01-19 16:18 completion after ../ Sven Wischnowsky
2000-01-19 18:44 ` Tanaka Akira
2000-01-20 4:34 ` Tanaka Akira
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).