broot VS lf

Definitely a fair sentiment. I personally like having a static visualizer handy because sometimes I just want to do a quick assessment rather than boot up an entire interactive CLI, but if interactivity is what you want broot has you covered :]

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

- will navigate via broot if it is a directory or will view it on a pager --bind 'ctrl-/:execute( if [[ -d {} ]]; then broot {} > /dev/tty else bat --paging=always -pf -l=sh {} > /dev/tty fi)' // Also can add another condition to check file-mimetype if an image to preview it

Broot is a tree alternative with a better user experience, and you can use it to navigate a file structure. It's fast and respects .gitignore. You can cd into a directory from the tree view, open sub-directories in a panel, and even preview files. It has excellent keyboard navigation as well. It has many more features.

broot

It's not. It's a DIY thingie which mostly creates the sh scripts you see at the root of my rust repos (exemple: https://github.com/Canop/broot) as well as a wrapper script deploying the docs and binaries to my server. Nothing high tech. I'll probably do a cargo utility someday for that but I don't think it will be useful for other people.

Also posted here: https://github.com/gokcehan/lf/discussions/1153

The clip above uses lf and the config is at https://github.com/jackielii/dotfiles/blob/main/.config/lf/lfrc Realistically, for each of these tools, you should be already using it. If you're starting from scratch, best place is the readme for each tool

Assuming you mean this then quoting from the man page.

documentation can either be read from terminal using 'lf -doc' or online at https://pkg.go.dev/github.com/gokcehan/lf You can also use 'doc' command (default '') inside lf to view the documentation in a pager. A man page with the same content is also available in the repository at https://github.com/gokcehan/lf/blob/master/lf.1

Well let me introduce you to lf, a terminal file browser. I love it. Any application that I use a lot gets the royal treatment (a 1 letter zsh alias).

FYI, switched to https://github.com/gokcehan/lf . Less functionality, but works for me for the moment.

LF. Has vi keybindings like ranger but faster and with async image preview. You may also need this or ranger's rifle as file opener

lf

I've used ranger for years, but recently replaced it with https://github.com/gokcehan/lf Mostly because the configuration is far, far simpler.

I like terminal file managers like lf, you can do both graphical and shell commands easily