"Failed to spawn fd" with picker when working in network drive

[Noghpu]

Hey there,

I'm on native Windows (lazyvim with default picker config) and want to work on a project that sits on a network drive. For some reason, the picker cannot spawn fd when the working dir is a network drive. Switching to fzf-lua works.

The picker works well otherwise and fd in the terminal also works on the network drive.

Any idea where to look for a solution?

[folke]

have you tried fd from the cmdline in that network drive and see what error you get?

[LJFRIESE]

I have just encountered this error as well, but I'm not on a network drive; I'm on WSL Ubuntu.

The default fd command in this distro is fdfind, but I have aliased it to fd. Both commands work correctly at the command line.

I have tried to change the command being invoked by the projects picker, but I'm not clear on the documentation . I tried both := Snacks.picker.projects({opts = {cmd = 'fd'/'fdfind'/'rg'/'find'}}) and := Snacks.picker.projects({cmd = 'fd'/'fdfind'/'rg'/'find'}), but in both sets of cases I'm still hitting the error (hence my thinking I've misunderstood the docs....)

Despite the error, the picker still seems to populate correctly. I'm just not sure if it would be different if the error were not occurring....

Any thoughts?

[gaven140]

same here, I am on a ubuntu based distro; I have also aliased fdfind to fd; didn't help. let us wait for fix/suggestions I guess

[folke]

Can you try again? The projects picker was using only fd.
Just fixed that.

[LJFRIESE]

Updated, works as expected, no more error :) Thanks!

[gaven140]

indeed, big thankz

[icecubez]

I also have the same problem. When I enter nvim from home dir (C:\Users\xxx), fd works fine and searchs only home dir. When I enter nvim from elsewhere (e.g. C:\ or D:), the error message ("Failed to spawn fd") comes up.

[folke]

Can you enable opts.picker.debug.proc = true?
Make sure you also enabled the notifier. Then do the search that fails.
It should now show a notification with the exact command.

[Stanton-B]

Anyone who has a similar fd issue on linux--a solution that worked for me was creating a symlink between fdfind and fd, as mentioned in a comment on the fzf github...I simply copy pasted the code in the below comment and explorer's search immediately started working:

Note that the binary is called fdfind as the binary name fd is already used by another package. It is recommended that after installation, you add a link to fd by executing command ln -s $(which fdfind) ~/.local/bin/fd, in order to use fd in the same way as in this documentation. Make sure that $HOME/.local/bin is in your $PATH.