zoxide VS broot

You can find all installations options in official GitHub repository.

One more tip:

https://github.com/ajeetdsouza/zoxide is amazing for returning to recent project folders from the CLI.

(Then I have a CLI command to open an explorer window. Directory Opus, actually)

Zoxide offical GitHub repo - https://github.com/ajeetdsouza/zoxide

Head over to ajeetdsouza/zoxide and install it now! It's innovative, free, and flexible!

I use this Rust clone which works great, no complaints: https://github.com/ajeetdsouza/zoxide

Although, I don't know what the difference is, other than the language of choice.

I use https://github.com/ajeetdsouza/zoxide, which is inspired by z and autojump.

Zoxide is basically the 'Rust Rewrite' version of the 'Z' tool and is actively maintained, I haven't had any issues with it: https://github.com/ajeetdsouza/zoxide

Indeed, utilities like zoxide which operate primarily as a cd replacement don't attempt to change directories via rust code - they create a shell alias that ultimately invokes a shell builtin to do it.

Would a commander type TUI work for you?

https://github.com/MidnightCommander/mc

https://github.com/ranger/ranger

https://github.com/jarun/nnn

There's also superfile and broot, but personally I feel like they try to do a little too much, might work for you though:

https://github.com/yorukot/superfile

https://github.com/Canop/broot

Take a look at broot https://github.com/Canop/broot

A past coworker implemented a system like this. It was awful. He was the gatekeeper because the numbers and names had to be "just so" to meet his approval, and he was the most senior person on the team. He was neurotic in general and a pain to work with.

The idea of limiting yourself to a few top-level categories in a directory hierarchy and then doing the same with subdirectories makes sense, but adding numbers is a bad idea. It just creates more work, and other people have to learn your idiosyncratic nomenclature. Just give the directories good names and get on with it. Search really isn't as bad as the article suggests, especially with something like broot [1].

[1]: https://github.com/Canop/broot

I've used a lot of the tools mentioned here in comments, but I think just for finding a directory/file broot[1] is much faster and easier than others. Though it is also quite feature rich but mostly it's just write a fuzzy search term that could even be sub-sub-directory and open, extremely quickly.

[1] https://github.com/Canop/broot

`broot` (https://github.com/Canop/broot) is another file manager with a curious interface that seems to fill a similar niche.

Of course, there are many other file managers to choose from (mc, ranger, nnn, lf, ....), but most of them don't show nested subdirectories by default.

As a macOS user, it boils my brain whenever I've to type in something like ~/Library/Application Support/org.rust-lang.Cargo/config.toml. macOS users have been begging CLI tools to support XDG variables on macOS too. Setting defaults is a strong indication to the community what should be the "preferred" locations. The defaults defined in your article will invariably lead to some authors saying that if that path is good enough for cargo, then it is good enough for their tool. Even the latest draft RFC acknowledges that macOS should use XDG variables too. I've written more about this here.

You may be interested in broot

I think you’re conflating different projects.

There are projects that aim for a better user experience, with better command line interface, defaults, performance and UI. These are of course breaking changes and the programs can’t be used as drop in replacement. Some examples are

- ls => exa (https://github.com/ogham/exa)

- grep => ripgrep (https://github.com/BurntSushi/ripgrep)

- cat => bat (https://github.com/sharkdp/bat)

- tree => broot (https://github.com/Canop/broot)

The person you’re replying to was speaking of a different project - uutils (https://github.com/uutils/coreutils). These are drop in replacements with identical interfaces (modulo bugs).

Even better broot, previously adding view verb to config: