search

ajeetdsouza / zoxide

A smarter cd command. Supports all major shells.
MIT License
20.54k stars 523 forks source link

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

Open kalocsaibotond opened 5 months ago

kalocsaibotond commented 5 months ago

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.

kalocsaibotond commented 5 months ago

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 commented 4 months ago

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

jan-bertle commented 4 months ago

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