[regression] zoxide is broken in nushell

[munzirtaha]

❯ zoxide init nushell | save -f zoxide.nu

❯ source zoxide.nu
zoxide: not a directory: /tmp/--

❯ nu --version
0.104.1

❯ zoxide -V
zoxide 0.9.8

[ajeetdsouza]

Seems to work fine for me.

Is there anything specific about your setup that you think might be causing the issue?

[munzirtaha]

You seem to be in macOS, I should have said my:

Operating System: Arch Linux

[Ezall2001]

i am experiencing the same problem
zoxide: not a directory: /path/to/dir/--

Linux asus-arch 6.14.7-arch2-1
nu: 0.104.1
zoxide: 0.9.8

Note;
it is changing dirs as expected but outputs that line each time

[ajeetdsouza]

I tried it on Linux as well, via a Docker image:

docker run -it --user root --rm ghcr.io/nushell/nushell:latest-alpine

Somehow, I'm still not seeing this error. But from what I gather from @stevenxxiu's PR, the following line in the zoxide init script seems to be causing the problem:

zoxide add -- $env.PWD

This seems like a Nushell bug more than a zoxide bug - it looks like Nushell is doing something with this double dash, rather than simply passing it on to zoxide.

[stevenxxiu]

This seems like a Nushell bug more than a zoxide bug - it looks like Nushell is doing something with this double dash, rather than simply passing it on to zoxide.

Where is the double dash supposed to be handled? Is it actually handled by the Zoxide binary in some Rust file?

[ajeetdsouza]

Where is the double dash supposed to be handled? Is it actually handled by the Zoxide binary in some Rust file?

Yup, it's actually quite common for CLI programs to allow a -- between the flags and the arguments. The -- denotes that there will be no flags after that point, to avoid confusion when handling args that look like flags themselves.

[stevenxxiu]

Ah thanks, I forgot that clap added that. I updated my PR.

[ajeetdsouza]

We're also tracking this issue here, if anyone is interested: nushell/nushell#15848

For now, I'd suggest not using the completions file till the issue is resolved.