Would The Garuda Team be opposed to including Zoxide out of the box?

[A_Metal_Penguin]

Ajeetdsouza’s Zoxide is tiny, Rust-built project.

"Zoxide is a smarter cd command, inspired by z and autojump.

It remembers which directories you use most frequently, so you can “jump” to them in just a few keystrokes.

Zoxide works on all major shells."

The main objection to including this, I suspect, would be that including Zoxide feels like it might be risky and ruin muscle memory (as well as perceived bloat).

However, Garuda already ships a highly tuned Fish/Zsh. Zoxide has the ability to overide cd (rather than use z or zi) with it’s functionality simply by adding zoxide init --cmd cd fish | source to the end of config.fish. This completely replaces the built-in cd with Zoxide’s version. No new commands for users to learn.

By doing so, muscle memory stays intact, navigation skyrockets, and now it feels like Garuda comes with magic.

For the bloat concern: the binary is <5 MB, RAM impact negligible, and obviously it can be uninstalled if anyone truly dislikes it.

Would it be a ridiculous idea for The Garuda Team to try including this and see the feedback? Is there any major objections to this idea?

[Technetium]

I agree that it is a cool project, but each deviation from “standard” behavior is an increase in complexity. I also have a slight personal aversion to overriding default binaries, for example I would expect posix compliant cd with all of its quirks. If I wanted to use zoxide, I would intentionally use z/zi, instead of (or alongside) cd. Maybe that’s just me being old and resistant to change though

The amount of people to initially benefit from this is rather small, so I’m not sure that it is worth adding. That said, it’s very simple for a user to add themselves via fish config as you’ve mentioned, so I don’t see the biggest justification to force it as a default.

Thanks for bringing this up

[A_Metal_Penguin]

Okeydokey! I appreciate your quick and honest response. Thank you for the consideration!