To wit (mocking a capistrano release structure):

Sandbox> mkdir cap
Sandbox> cd cap
cap> mkdir -p shared releases/{1,2,3}
cap> ln -s "$PWD"/releases/3 current
cap> cd current
current> ls ..
current/  releases/
current> ls ..<TAB>        # bash completes to ../
current> ls ../<TAB>
current/  releases/
current> ls ..<TAB>         # zsh does not complete
Completing `files' or `corrections'              # nor provides results
current> ls ../<TAB>       # zsh provides results
Completing files
1/  2/  3/
current> cd ..     # both go back up the symlink

Bash is extremely pernicious, because when you swap ls for e.g vim and try to edit a file in shared from inside current, it will autocomplete but it won't work.

Zsh does it right though (compared to bash), by clearly separating interactive navigation from command execution, thus only using the symlink as pwd for navigation and in $PWD, otherwise resolving the symlink for command and argument autocompletion, and by making use of the convention or method that consists of resolving symlinks when using a final slash (foo vs foo/, see point 3).

The reasoning is that the mental model of the user doing cd foo; cd bar; cd baz is equivalent to doing cd foo/bar/baz by way of pushing levels of the tree hierarchy onto some stack, and that doing cd .. is equivalent to popping a logical level. The consequence is that bash/zsh lazily resolves the symlink, whereas fish eagerly resolves it.

When scripting, the most robust solution to 'go back up' is certainly to never use cd .. but cd while inside a subshell, or leverage a real stack using pushd/popd/cd - (does fish have those?).

When interactive, should I cast a vote, I'd probably go with the above mental model, however 'unpure' it may look like.

Either way, this can't be an option, or it'll subtly break script behaviour consistency across setups with different settings, unless they start with some shopt-like stuff forcefully, which I'm quite sure is a territory the fish authors don't want to enter.

Uh oh!

Uh oh!

cd into symlink results in suprising behavior. #1957

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions