rust-musl-cross
broot
Our great sponsors
rust-musl-cross | broot | |
---|---|---|
5 | 41 | |
572 | 10,102 | |
3.7% | - | |
7.2 | 9.1 | |
24 days ago | 12 days ago | |
Shell | 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.
rust-musl-cross
- How do I cross compile for Rasperry Pi 64 bit on Windows?
-
Hey Rustaceans! Got a question? Ask here! (36/2022)!
Is my best bet just to use (rust-musl-cross)[https://github.com/messense/rust-musl-cross] as the builder image?
-
Guidance about cross compilation tools, especially targeting musl
rust-musl-cross: active as last commit was 10 days ago. It said it based on rust-musl-builder. But this repo was created years ago. So why would this exist when there is also rust-musl-builder. What are the differences compared to rust-musl-builder and muslrust?
-
Running Rust on AWS Lambda on ARM64
The example that is provided in the AWS Rust runtime repository shows them using a custom linker and rustup target in order to cross-compile for x86-based lambdas. I attempted to dive into how to get a arm64-based linker, but in the process of trying to figure out how to get that linker installed locally (no convenient packages for Ubuntu, sorry), I stumbled across a project that provides cross-compilation tooling for various platforms via Docker. That made my life a lot easier - Using the rust-musl-cross Docker container, all I have to do is wrap the call to cargo build, and it builds for the proper architecture:
- rust-musl-cross docker images added linux/arm64 architecture support
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?
docker-rust - The official Docker images for Rust
fzf - :cherry_blossom: A command-line fuzzy finder
rust-on-raspberry-pi
nnn - n³ The unorthodox terminal file manager
docker-ipsec-vpn-server - Docker image to run an IPsec VPN server, with IPsec/L2TP, Cisco IPsec and IKEv2
xplr - A hackable, minimal, fast TUI file explorer
docker-rustup - Automated builded images for rust-lang with rustup, "the ultimate way to install RUST"
zoxide - A smarter cd command. Supports all major shells.
muslrust - Docker environment for building musl based static linux rust binaries
lf - Terminal file manager
aws-lambda-rust-runtime - A Rust runtime for AWS Lambda
voidrice - My dotfiles (deployed by LARBS)