Match forward slashes on Windows

[dkaszews]

With ~\foo\bar\meow being a previously visited directory, cd bar\meow works, but cd bar/meow does not, unless already in ~\foo.

[JeetKarena]

Issue

With ~\foo\bar\meow being a previously visited directory, cd bar\meow works, but cd bar/meow does not, unless already in ~\foo.

What is happening?

Suppose you've previously visited:

C:\Users\Alice\foo\bar\meow

so zoxide has it in its database.

Now you're somewhere else, for example:

C:\Users\Alice

Running:

cd bar\meow

works because zoxide recognizes bar\meow as a relative path pattern and matches it against its database.

However,

cd bar/meow

does not work, even though Windows itself accepts / as a path separator.

Interestingly, if you're already inside:

C:\Users\Alice\foo

then

cd bar/meow

works because the shell resolves it as a normal relative filesystem path before zoxide needs to search.

---

Why this is a bug

Windows APIs generally accept both:

bar\meow

and

bar/meow

as equivalent paths.

zoxide appears to normalize or match only backslashes (\) when performing database lookups, causing forward-slash patterns to fail unless they already resolve as ordinary filesystem paths.

---

Expected behavior

Both commands should behave identically:

cd bar\meow

cd bar/meow

Both should resolve to:

C:\Users\Alice\foo\bar\meow

using the zoxide database.

---

Possible implementation fix

Before matching user input against the database, normalize path separators on Windows, for example:

query = query.replace('/', "\\");

or use a platform-aware path normalization routine (std::path::Path) so that / and \ are treated equivalently during matching.

This would make zoxide behave consistently with native Windows path handling.