zoxide: no match found can be too easily confused with zoxide: command not found

[AltiorRonan]

When you type a command like z an-absoloutly-unkown-directory, the response is zoxide: no match found which can be too easily confused with the fact that the command z does not exist (zoxide: command not found).

A better message would be: zoxide: no match found for 'an-absoloutly-unkown-directory' which is a better distinction between zoxide vs OS error message.

[azaleacolburn]

Generally, I agree. One issue with this though is that multiple keywords can be used in a query, e.g., zoxide foo bar.

I propose that it be formatted as such:
zoxide: no match found for 'foo' and 'bar'.

[ajeetdsouza]

That seems to me like it would be very verbose. It's also redundant, since the query on most shells would be visible right above the error:

$ z foo bar
zoxide: no match found for 'foo bar'

It would also be slightly confusing in places:

$ z "foo bar" baz
zoxide: no match found for '"foo bar" baz'

Lastly, the case we're optimizing for (zoxide: command not found) seems like it would not happen very often on most setups - it seems like we're optimizing for 1% of situations at the expense of the remaining 99%.