# ssh: Fix incorrect handling of ssh paths that exist locally \(\#33743\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/f785853239ab2344cf1677b89cdf039ec3b6877c)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: f785853239ab2344cf1677b89cdf039ec3b6877c

Requested commit: f785853239ab2344cf1677b89cdf039ec3b6877c

Commit: f785853239ab2344cf1677b89cdf039ec3b6877c

Tree: 9f1b71bdb4f4bdc90b7273448eab91234a1e4c1d

Author: Peter Tripp

Committer: GitHub

## Message

```
ssh: Fix incorrect handling of ssh paths that exist locally (#33743)

- Closes: https://github.com/zed-industries/zed/issues/33733

I also tested that remote canonicalization of symlink directories still
works. (e.g. `zed ssh://hostname/~/foo` where `foo -> foobar` will open
`~/foobar` on the remote).

I believe this has been broken since 2024-10-11 from
https://github.com/zed-industries/zed/pull/19057. CC: @SomeoneToIgnore.
I guess I'm the only person silly enough to run `zed
ssh://hostname/tmp`.

Release Notes:

- ssh: Fixed an issue where Zed incorrectly canonicalized paths locally
prior to connecting to the ssh remote.
```

## Parents

- [82aee6bcf70f4d1039f748e6922545c79a534a18](https://git.cafe/gitcafe/zed/commit/82aee6bcf70f4d1039f748e6922545c79a534a18?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/f785853239ab2344cf1677b89cdf039ec3b6877c?format=markdown)