rust-musl-builder
broot
rust-musl-builder | broot | |
---|---|---|
3 | 41 | |
1,514 | 10,134 | |
- | - | |
0.0 | 9.1 | |
7 months ago | 2 days ago | |
Dockerfile | Rust | |
Apache License 2.0 | 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.
rust-musl-builder
-
Guidance about cross compilation tools, especially targeting musl
rust-musl-builder: most popular in the musl compilation category, seems to be abandonned due to the removal of Docker Hub free tier as last commit was on Feb 13, 2021 with a lot of issues request updating to the newest stable Rust
-
Cross Compiling - Having issues with musl-gcc across 2 programs
This might help: https://github.com/emk/rust-musl-builder
-
Vscode + Remote SSH - Is it the way to explore for rust programmers with Mac in 2021?
Normally, you would not need it if architecture is the same. But there might be problems with specific libs and this is why docker/vms might be required: https://github.com/emk/rust-musl-builder
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?
actix-web - Actix Web is a powerful, pragmatic, and extremely fast web framework for Rust.
fzf - :cherry_blossom: A command-line fuzzy finder
The FastCGI Rust implementation. - Native Rust library for FastCGI
nnn - n³ The unorthodox terminal file manager
Rocket - A web framework for Rust.
xplr - A hackable, minimal, fast TUI file explorer
heroku-buildpack-rust - A buildpack for Rust applications on Heroku, with full support for Rustup, cargo and build caching.
zoxide - A smarter cd command. Supports all major shells.
urlshortener-rs - A very-very simple url shortener (client) for Rust.
lf - Terminal file manager
docker-rust - The official Docker images for Rust
voidrice - My dotfiles (deployed by LARBS)