z VS broot

- Visidata

- z (https://github.com/rupa/z)

- fzf

- vim

- Fastmail

- WireGuard

- draw.io

- PowerShell (it’s difficult to overstate how much PS has improved Windows system administration)

- Microsoft PowerToys

- WSL (alternating joy and extreme frustration)

- Home Assistant

- Airfoil

For even more power use z

https://github.com/rupa/z

- quickly jump to recent directory: https://github.com/rupa/z - however I find it kinda annoying it seems to forget/ignore(?) directories, anyone know of a better version of this?

- quickly opening my personal wiki: https://github.com/francium/dotfiles/blob/master/bin/.local/...

- re-run a script when a file changes: https://github.com/francium/dotfiles/blob/master/bin/.local/...

For `while-watchdo` you, you run it like `while-watchdo "echo hi"`, then in my editor, I have a custom shortcut that does `touch .watchfile` causing the command, in this case `echo hi` to run. I prefer this to tools that retrigger commands as soon as you save _any_ file. Also works in docker containers, edit a file on host, command runs in a container.

2) Well friend, this is where you can have the best of both of worlds. You can just open the file explorer via the CLI. Typically you'll have the xdg-open command that opens the directory in your default file browser. I have that aliased to xdgo. So you can navigate quickly to where you need to be, and then open it visually with xdgo . . There's also other really convenient navigation tools like z (https://github.com/rupa/z) that I can't imagine going without anymore.

I would like to know how you use the terminal and nvim in your daily workflow. Here is mine: I have a shortcut (with raycast) to open alacritty full screen from anywhere. I open alacritty and start the tmux (create work and personal sessions). Then using z navigate to the desired project. Next, I have a bash script pde that opens nvim, and 2 terminal splits below. Nvim opens with alpha-nvim (startify theme). For file explorer I use lir.nvim. Fuzzy finding using fzf-lua. I have harpoon but don't use it very often, instead, I manage buffers with fzf-lua and vim-bbye. When working on multiple files I usually have 2-4 vsplits. I do git stuff mostly using vim-fugitive (gv.vim, resetting hunks with gitsigns.nvim), occasionally git commands from another tmux window. I use auto-save.nvim. My most used command is :F (lsp.bug.format). For movements I use Ctrl+D/U/O/I/, sometimes relative line jumping. Other often movements [q,]q (quickfix jumps), [d,]d (diagnostics jumps), [c,]c (Gitsigns hunks). Alacritty + Neovim view

For general filesystem navigation in my terminal, I'm using z command. But for finer control, I am using the following commands.

z

Do you know about the program z? https://github.com/rupa/z

https://github.com/rupa/z is an awesome command to teleport to your most used directories. It's really handy to jump from a project to another.

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:

Broot: https://github.com/Canop/broot