From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@math.gatech.edu
Subject: Re: bug 3.1.5 symlinks & cd
Date: Mon, 16 Nov 1998 10:28:01 +0100 (MET) [thread overview]
Message-ID: <199811160928.KAA10354@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Phil Pennock's message of Fri, 13 Nov 1998 21:19:08 +0000 (GMT)
Phil Pennock wrote:
>
> Using a stock zsh-3.1.5, there seems to be some problem with completion
> using one interpretation of a directory tree with symlinks, and cd using
> another. (Linux 2.0.x on x86.)
>
> % zsh-3.1.5 -f
> machinename% PS1='%~%# '
> ~% mkdir tmp/tst && cd tmp/tst
> ~/tmp/tst% mkdir foo foo/bar wibble
> ~/tmp/tst% ln -s foo/bar .
> ~/tmp/tst% cd bar
> ~/tmp/tst/bar%
>
> At this points, try tab-completing "cd ../" and you get "../bar", try
> ../w<tab> and it beeps. Try "../../w<tab>" and you get the wibble
> directory completed, but:
>
> ~/tmp/tst/bar% cd ../../wibble
> cd: no such file or directory: ../../wibble
> ~/tmp/tst/bar% cd ../wibble
> ~/tmp/tst/wibble% compctl -L cd
> compctl: no compctl defined for cd
>
> Note that the ../wibble refuses to tab-complete.
Damn. Currently I see no simple solution for this. It looks as if we
would need a compctl flag for completing paths with special sym-link
handling just for `cd' and friends which seem to be the only builtins
that use CHASESYMLINKS for their arguments.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1998-11-16 9:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-16 9:28 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-11-18 13:41 Sven Wischnowsky
1998-11-18 9:09 Sven Wischnowsky
1998-11-18 13:06 ` Peter Stephenson
1998-11-18 19:25 ` Bart Schaefer
1998-11-18 22:41 ` Phil Pennock
1998-11-13 21:19 Phil Pennock
1998-11-14 5:48 ` Bart Schaefer
1998-11-15 3:01 ` Phil Pennock
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199811160928.KAA10354@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@math.gatech.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).