Paths on WSL2 to Windows paths appends '\r' making it unusable

[genotrance]

> ls -l /home/user/mnt
...
onedrive -> /mnt/c/Users/UserName/OneDrive
...

> zoxide edit
...
SCORE PATH
  1.0 /home/user/mnt/onedrive/docs

> z docs
-bash: cd: $'/home/user/mnt/onedrive/docs\r': No such file or directory

The \r needs to be stripped from paths.

[ShedFlu]

Hey @genotrance ,

I feel like this is very much an edge case that might be too rare to add a fix to zoxide itself. I don't have this issue on my WSL instances and failed to reproduce it artificially, but I still might have a workaraound for you.
Just in case you still need this or someone else has a similar issue:

The main problem I see with a fix is that \r is a valid character in file/pathnames and shouldn't be stripped away willy nilly.
So my idea for a fix is simply to try cd and if that fails, try again after stripping \r from the end

Somthing like this would need to be placed after zoxide's init (eval "$(zoxide init bash)") in your bashrc:

# helper that strips carriage return from the end of a string
__zoxide_rstrip_cr() {
  \builtin local s=${1-}
  while [[ $s == *$'\r' ]]; do s=${s%$'\r'}; done
  printf '%s' "$s"
}
# override of zoxide's cd that tries again with the modified arg after failing
__zoxide_cd() {
  \builtin cd -- "$@" && return 0
  if [[ $# -eq 1 && $1 == *$'\r' ]]; then
    \builtin cd -- "$(__zoxide_rstrip_cr "$1")"
  fi
}

simple tests of __zoxide_rstrip_cr

I used xxd -b to test the function, since it's easy to see and compare the byte count.

# echo as a baseline

$ echo -n $'test' | xxd -b
00000000: 01110100 01100101 01110011 01110100                    test

$ echo -n $'te\rst' | xxd -b
00000000: 01110100 01100101 00001101 01110011 01110100           te.st

$ echo -n $'test\r' | xxd -b
00000000: 01110100 01100101 01110011 01110100 00001101           test.

$ __zoxide_rstrip_cr $'test' | xxd -b
00000000: 01110100 01100101 01110011 01110100                    test

$ __zoxide_rstrip_cr $'te\rst' | xxd -b
00000000: 01110100 01100101 00001101 01110011 01110100           te.st

$ __zoxide_rstrip_cr $'test\r' | xxd -b
00000000: 01110100 01100101 01110011 01110100                    test

I started from zoxide init bash's output and tweaked it, the init is different for bash, zsh, fish, and so on, so you might need to rewrite it a bit to fit your prefered shell.
I don't have onedrive and can't test that exact path myself, but adding it doesn't break anything on my instances.

Hope this helps :)