xplr
broot
Our great sponsors
xplr | broot | |
---|---|---|
104 | 41 | |
3,943 | 10,102 | |
- | - | |
8.3 | 9.1 | |
19 days ago | 12 days ago | |
Rust | Rust | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
xplr
-
Which is Best TUI file manager
I use xplr and like it very much.
-
Midnight Commander is MIA; any command line based twin pane file manager recommendations?
xplr
-
[Projet] PIC 📷
PIC stands for Preview Image in CLI, I think this should be explicit enough. I first made it because I needed a way to display images in the terminal (for an xplr plugin), but the more I worked on it, the better it got, as of now I have implemented 4 different ways to preview images (I couldn't find other ones), some can even display GIFs!
-
Telegraph and the Unix Shell
Certain file managers like xplr allow for more advanced terminal UX. Check out the video on https://xplr.dev/ and you can see something like a live/interactive ls that allows toggling arguments (instead of running multiple commands and pushing previous stdout further into the past).
-
xplr v0.20.0 - what's new?
xplr version 0.20.0 was released last week. If you haven't already, go ahead and install the latest version. This post will try to break down the changelog in the release in an easy-to-digest manner, looking through the perspective of different user groups.
-
ranger-like three pane layout for xplr file explorer written in rust
Tool: https://xplr.dev
-
Ask HN: Is it still possible to live in a terminal?
The Vim/Neovim ecosystem has gotten unbelievably better over the last 5-10 years. "Living in the terminal" for core development work is IMO better than pretty much anything else out there; my Neovim setup has a modern plugin manager; an IDE-like experience with fast autocompletion as I type, goto definition, and automated refactor support; and a side-drawer file browser navigable with Vim motions. It feels like an IDE, except that it launches in ~100ms and has ultra-low typing latency. Using it with tmux panes means I can have various drawers and panes with a series of full, incredibly fast terminals wherever I want, with long-running tasks like automated test watching/running while I edit code placed wherever I want around the editor panel. Not to mention the Cambrian explosion of "modern" terminal tooling getting built, like xplr [1], hyperfine [2], httpie [3], etc.
That being said, I think "living in the terminal" for general purpose computing, like browsing the web or talking to your coworkers, has been in a kind of frozen standstill while the rest of the world has moved on. I think it isn't worth trying to push non-dev work into the terminal currently.
1: https://github.com/sayanarijit/xplr
2: https://github.com/sharkdp/hyperfine
3: https://github.com/httpie/httpie
-
LF, NNN or ViFM?
a terminal file manager built in rust I just heard about
- xplr released with built-in fuzzy search based on skim v2 algorithm
-
how to rm -rf ~/Desktop permanently?
I tried using nnn but didn't find it easy to adopt, now I'm looking at https://github.com/sayanarijit/xplr
broot
-
Use Midnight Commander like a pro (2015)
Take a look at broot https://github.com/Canop/broot
-
Johnny Decimal: A System to Organize Projects
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
- Broot: A new way to look at file management written in Rust
-
Antonmedv/walk: Terminal file manager
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
-
Projectable: A TUI file manager built for projects
`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.
-
Report on platform-compliance for cargo directories
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.
-
erdtree v1.2.0, a modern multi-threaded alternative to `du` and `tree` now with support for globbing, icons, and more
You may be interested in broot
-
bsdutils: Alternative to GNU coreutils using software from FreeBSD
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).
-
Reading Ebooks on the Commandline
Even better broot, previously adding view verb to config:
-
Is possible to configure "micro" terminal text editor with "broot" tool, to open text file with micro?
Broot: https://github.com/Canop/broot
What are some alternatives?
nnn - n³ The unorthodox terminal file manager
fzf - :cherry_blossom: A command-line fuzzy finder
lf - Terminal file manager
ranger.vim - Ranger file manager for Vim
zoxide - A smarter cd command. Supports all major shells.
nnn.vim - File manager for vim/neovim powered by n³
joshuto - ranger-like terminal file manager written in Rust
voidrice - My dotfiles (deployed by LARBS)
nixos - My NixOS Configurations
rav1e - The fastest and safest AV1 encoder.