Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Zoxide does not register directories at network location on Windows 10 with Powershell #677

Open
kalocsaibotond opened this issue Jan 29, 2024 · 3 comments · May be fixed by #682
Open

Zoxide does not register directories at network location on Windows 10 with Powershell #677

kalocsaibotond opened this issue Jan 29, 2024 · 3 comments · May be fixed by #682

Comments

@kalocsaibotond
Copy link

kalocsaibotond commented Jan 29, 2024 •
edited

I have played around with zoxide and it seems to be quite an improvement compared to the version of z written in Powershell (available in scoop).
However, when I had to jump around between the depths of the folders of my computer and the folders of a server shared network directory, I realised that no matter how much I traverse the relevant workdirs in the server folder, zoxide did learnt it at all. It does not show up when I look up the registered folders with the zi command. Meanwhile the Powershell version of z learnt it without a problem.

I hope this shortcoming is a bug and not an intended feature because it delimits the utility of zoxide.

I am utilising Windows 10 Pro, Version 22H2 (OS Build 19045.3930) for OS. I am utilising the cross-platform Powershell 7.3.6. Both the cross-plaftorm Powershell and zoxide 0.9.2 was installed with scoop.
@PaysanCorrezien PaysanCorrezien linked a pull request Feb 7, 2024 that will close this issue
Open
@kalocsaibotond
Copy link
Author

I have tried out the recent patch of zoxide for the same problem and it did not changed.
I scooped the 0.9.3 version. The problem remains the same.

@vablings
Copy link

vablings commented Mar 4, 2024

If you point directly to a mapped drive rather than the UNC path, zoxide will work correctly if you need a workaround.

@jan-bertle
Copy link

on 0.9.2 the same thing happens and not even using the network drive letter works. using the unc path i get "invalid path", while for the network drive letter it says "not a directory" which is also strange

@kalocsaibotond kalocsaibotond mentioned this issue Mar 19, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

add support for windows UNC path PaysanCorrezien/zoxide
3 participants
@vablings @kalocsaibotond @jan-bertle