Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: bug 3.1.5 symlinks & cd
- X-seq: zsh-workers 4637
- From: Phil Pennock <phil@xxxxxxxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxxx
- Subject: Re: bug 3.1.5 symlinks & cd
- Date: Sun, 15 Nov 1998 03:01:58 +0000 (GMT)
- Cc: schaefer@xxxxxxxxxxxxxxxx
- In-reply-to: <981113214816.ZM19988@xxxxxxxxxxxxxxxxxxxxxxx> from Bart Schaefer at "Nov 13, 98 09:48:16 pm"
Typing away merrily, Bart Schaefer produced the immortal words:
> On Nov 13, 9:19pm, 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.
>
> This isn't new. It behaves the same way in 3.0.5. `setopt chaselinks'
> will make the effect go away.
Yes, but:
CHASE_LINKS (-w)
Resolve symbolic links to their true values when
changing directory.
The 'effect' only goes away insofar as this avoids the problem by never
having a symbolic-link as part of PWD.
If you want to have the 'real' view of a layout, fine. But forcing this
option just to get a consistent interpretation of the FS dodges the fact
that two different parts of the shell are taking differing approaches to
symbolic-links pointing to directories. Completion ignores the symbolic
aspect of PWD, such that a ../ always uses the underlying 'true' layout,
whilst cd handles the symbolic links. This is a conflict that's
entirely due to two parts of zsh doing things very differently.
$0.01 (discounted 50% -- as Bart says, it can be worked around, but it
shouldn't have to be.)
--
-Phil 'my paragraphs naturally right-align' Pennock
Messages sorted by:
Reverse Date,
Date,
Thread,
Author